PHP project packaging method Page 1/2_PHP tutorial

Corporate websites are easy to say, at least they need a virtual host or something; but OA, finance... these internal systems are hard to say. You can't just throw the code and database to others, write a description, and let them configure the environment according to the instructions. Install the code. This is obviously outrageous. You must know that every other line is like a mountain! Furthermore, if the customer is thousands of miles away from where he or she lives, he can't go there and have someone install it. In this case, all the income will probably not be able to cover the cost of the trip. Therefore, it is necessary to package the WAMP environment + PHP program + maintenance installation and uninstallation program into an EXE installation package. Let customers install PHP programs as easy and convenient as installing QQ!

There should be multiple methods. There are only three that I know of.

Use RAR’s automatic decompression function.
Use Windows packaging software InstallShield to create an installation package.
Pack with ready-made items! (Haha, as the saying goes, you stand on the shoulders of giants! I am also a lazy person.)
As for the above 1.2 method, you can search it through Baidu and Google. I'm not too lazy to search...=.=! Better than me...

Here I will explain my method in detail. This method was also collected by me when I helped a friend build a real estate information system a few days ago.

First, you need a pure and green PHP operating environment. Components are configured first according to project requirements. I use F:PHPServer as the environment root directory. The general components apache2+php5+mysql5+zo need to open the GD library... configure 80, 3306... everyone should be familiar with this than me. It is best to use a highly customizable integrated suite, preferably a green version in ZIP format, such as PHPNOW and XAMPP. Don't worry, the download link will be written below. I use PHPnow, which is compact, convenient and highly customizable!

Second, install our compiled system, check and debug by yourself, and everything is OK. Okay, that's half done. At this time, someone spoke up, "charlatan", "Mongolian doctor" and "liar". kindness! Don't be impatient, the fun is coming! Now in this folder PHPServer, we must ensure that no configuration files are imported from the outside world. We must ensure the independence and integrity of PHPServer, that is, ensure that it is green.

Third, these green integration suites generally have written BAT, which is a batch file, and you can start and shut down the service by directly entering the number. At this time, we can use RAR self-extraction + run batch processing, which is fine, but now it is blocked by many anti-virus software. In fact, I also use this principle. I found a packaging program make_exe (from PHPnow) on the Internet that can package the .7z+ file interface information into an EXE running package, and automatically run the batch file in the 7z compressed package after running the self-extraction. The make_exe.zip package contains three files: Make_exe.cmd, PHPServer.sfx, and PHPServer.sfx.cf. Seeing this, everyone should have an idea. First, compress PHPServer into PHPServer.7z file and then configure it. Just modify the PHPServer.sfx.cf file and run Make_exe.cmd.

First: Make_exe.cmd code

set v=1.2
copy /b /y PHPServer.sfx + PHPServer.sfx.cf + *.* PHPServer%v%.exe | | pause
It’s obvious! "set v=1.2" is the version, and then three files are needed for packaging.
PHPServer.sfx.cf code, open the method and drag it directly to TXT