deployment archive

dylan's picture

Parse / extract server settings from your Capfile

One interesting thing that has evolved from our use of Capistrano is the configuration files have become the de-facto documentation hub for a project's server connection details. (We do maintain inventory data elsewhere, but for the developer in the trenches, config/deploy/prod.rb is the first place to look). A question arose: How to parse the settings out of these files? Read More…

kronda's picture

Avoid Potholes When Deploying Drupal Sites to Media Temple Virtual Private Servers

I recently had occasion to set up a new Drupal site on a dedicated virtual private server on Media Temple (dv 4.0). Everything was going swimmingly until I deployed the site and tried to reach it via the IP address. The result was the install.php page, even though my settings file was uploaded and had the correct settings for the database. To make matters more frustrating, the log files were not located in the standard place (/var/log/httpd/domain.com-error.log) After some searching we* finally found them at /var/www/vhosts/domain.com/conf/ and found that the particular file that contained the database settings was causing a 403 error - access forbidden. Read More…

dylan's picture

Deployment with Capistrano Part 2: Drush integration, Multistage, and Multisite

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 task definitions described here). Multistage: Deploy to different environments (such as testing vs. production). Drush Integration: Use the power of Drush to extend Cap's reach into Drupal's internals. Multisite: Run many sites from a single code base. Read More…

Pages