Capistrano Deploy to dynamic AWS EC2
At Metal Toad we use Capistrano to deploy our projects to their respective servers.
When we added the Compass CSS authoring framework to our projects, new wrinkles appeared in the deployment process. Committing the artifacts to Git was used for our first prototypes, but is unsuitable for team projects because it's a sure-fire way to introduce merge conflicts. Running compass on the server (either with Cap or the Drupal module) is appealing, but a minority of our projects deploy to hosts without the ability to install Compass. Rather than support multiple strategies, we decided on executing Compass locally on the workstation running Capistrano. Changes are needed to several files:
At Metal Toad we use Capistrano to deploy our projects to their respective servers.
In my last post, a basic intro to to running cap deploy was presented. Now, let's look at some more advanced scenarios. (See Part 1 for the actual...
Resolving Capistrano upload errors by utilizing the :mkdir option in net-sftp to ensure target directories are created during deployments.