To keep track of the bugfixes we'll need to make for our next release, I've created a Subversion branch called branches/release-1. Development of new features will continue on trunk, but we'll merge in the bugfixes from release-1 every so often.
There are three environments we deploy to:
- Developers should be able to easily test both versions on their local machines.
- QA server
- We should be able to deploy both versions to a publicly-accessible QA server for acceptance testing.
- Production server
- We should be able to deploy release-1 (and then later, release-2 and so on) to the production server, preferably after a lot of testing
Editorial changes happen on the production server, where our users update content. We would like to be able to take a snapshot of that database and use that to test our development code on the QA server or in our local development environments. Because we use Domain Access
to serve multiple subdomains with shared content, it's not just a matter of using mysqldump
to back up the database and copy it over. We also need to replace URLs inside the database, and we need to override
array in settings.php.
I'm the only one running Linux, so the other developers don't really benefit from the Makefiles I've defined or the tools I use. For the simpler build system we had before (all development on trunk), I wrote a deployment script that allowed users to:
- Download a stripped copy of the production database with the URLs changed for their local testing environment
- Deploy a stripped copy of the production database to the QA server
- Deploy a specified revision of the source code to the QA server
- Deploy a specified revision of the source code to the production server
The new deployment script needed to allow users to do the same, but for both branches of the code. Both branches of the code would be simultaneously available on the QA server, so the script would need to deploy the code to different directories.
After some fiddling around with the page design (because I care about making interfaces make sense!), I came up with something that looks like this:
The deployment script allows the user to get a copy of the database, deploy a copy of the database, or deploy specific revisions of branches.
Because I was having a hard time figuring out how to do ssh key-based operations from Apache (which runs as a no-login user), I use two shell scripts to do the dirty work. One shell script connects to the production server, creates a partial backup, copies the information over, and does any necessary replacements. Another shell script takes a domain name and optionally a revision, and deploys the revision from the appropriate branch.
Here's my totally small-scale PHP way to show the revisions log:
$dev_output = shell_exec("svn log $dev_url $details --limit 20");
$dev_revisions = preg_match_all('/r([0-9]+)/', $dev_output, $dev_matches);
is the URL of the trunk in Subversion, and $details contains the username and password specified as options for the Subversion command-line.
I'm going to see if I can get my regression tests running on the server that I've got my deployment script on. Wouldn't that be awesome?