PUBLIC MARKS with tags drupal & deployment

The goal of automating deployment is to make introducing new features easier. In this post we will learn how to set up a workflow that will move code and configuration of your drupal site from your local development station, to development, to staging and to production all by a using your version control and a push of a button.

This article covers best practices and recommendations from Acquia Support for moving builds from staging to production, to help standardize client build processes. It covers moving code into the staging area, and migrating databases.

Drupal And Linux, A Deployment Script

Creating a module update function to disable your development modules when deploying to production

Features is part of the answer to one of Drupal’s biggest headaches – what to do with all that loose site building and customization that happens on every project. Features is part of the answer to making stronger, better install profiles and targeted distributions of Drupal. And features is part of the answer to making Drupal more task oriented and less daunting to our users.

Anyone who has developed a relatively complex Drupal site will be able to vouch that, while launching a new site is relatively simple, continuous integration becomes very tricky once the site has actually gone live. This problem becomes especially pronounced when there is more than one developer on a project, and when the project is being built using proper development methodology.

The deployment framework is a series of modules which are designed to allow developers to easily stage Drupal data from one site to another.