Automated Builds
Deploying enterprise code requires an automated build tool to save developers time and reduce mistakes while allowing us to maintain the code for multiple servers. For Php, that tool is Phing. Our build process begins with checking out the tested code from our version control repository. The scripts then auto-generates formatted documentation built from our informative comments embedded in the Php files, along with a changelog and notification emails, all automatically. It then resets the application's environment to "production", which automatically uses the production server's passwords and other specific settings.
Upload and Checkout
After we run the build tool, its time to upload the feature's code to the production server. We use only SFTP over SSH to communicate with any server we touch. Using SFTP instead of regular FTP is much more secure and prevents sensitive settings from possibly being read as the code travels through the internet to your production server. After, we run a checkout of a set of tests one more time to ensure that the difference in server configuration does not break the application.
Repeat the Process!
Once deploying the feature, we go back to step 1 and begin the next feature until we complete your web application.
Further reading
- Ask Questions
- Phing build tool
