Community Documentation

Comparison of staging and deployment modules

Last updated October 9, 2011. Created by coderintherye on November 23, 2010.
Edited by naught101, imclean, s1l, hefox. Log in to edit this page.

Many site admins wish to backup, create snapshots, stage and deploy sites, both on the same server as well as on external servers. Below is an attempt at listing the features of modules that support such activity.

It should be noted that there are big differences between content, code, and configuration deployment. Some of these modules are designed for a particular use only, some work for a few.

Note, migrate modules are simply listed as "yes" for both import and export.
Module
Main Aim
content
config
code
export
import
Last row update
Deployment Content staging
yes
no
no
yes
yes
9 Oct 2011
Stager Staging content and config
yes
yes
no
yes
yes
9 Oct 2011
Snapshot Backup a whole site, code and database
yes
yes
yes
yes
no
9 Oct 2011
Backup
& Migrate
Backup the whole database, and import
yes
yes
no
yes
yes
9 Oct 2011
Drush
Make

Installs all code for a site from a .info file
no
no
yes
no
yes
9 Oct 2011
Drush
Deploy

Code deployment using drush
no
no
yes
yes
yes
9 Oct 2011
dog
(Drupal on Git)

Aims to enable site code deployment over git,
via drush
no
no
yes
yes
yes
9 Oct 2011
Staging
Sync two sites
?
?
?
?
?
9 Oct 2011
Features
Saves config setups that satisfy certain
use-cases
no
yes
yes
yes
yes
9 Oct 2011
Migrate
Migrate content from/to any source (Drupal,
wordpress, other CMS, spreadsheet, whatever)
yes
no
no
yes
yes
9 Oct 2011
Backup
back up a whole site, code and database
yes
yes
yes
yes
no
9 Oct 2011
Yet Another Migrate
Module

Mass content synchronisation
yes
?
no
yes
yes
9 Oct 2011

Development status

Module
5.x
6.x
7.x
#commits
#users
Development
Last row update
Deployment no
alpha
dev
~200
614
active
9 Oct 2011
Stager no
no
1.2
13
19
minimally
maintained
9 Oct 2011
Snapshot no
0.1
no
1
110
appears
abandoned
9 Oct 2011
Backup
& Migrate
1.3
2.4
2.2
214
100,696 active
9 Oct 2011
Drush
Make

no 2.3
no
~450
N/A
active
9 Oct 2011
Drush
Deploy

no
no
no
13
N/A
active
9 Oct 2011
dog
(Drupal on Git)

no
no
no
~110
N/A
active
9 Oct 2011
Staging
no
0.1
no
5
9
appears
abandoned
9 Oct 2011
Features
no
1.1
beta
~100
~40,000
active
9 Oct 2011
Migrate
no
2.2
2.2
~1100
2706
active
9 Oct 2011
Backup
3.0
no
no
?
212
abandoned
9 Oct 2011
Yet Another Migrate
Module

no
rc3
no
25
11
active
9 Oct 2011

Please update this page to reflect your knowledge of these modules

Comments

Feature comparison

Feature comparison between the modules would be handy. For example, Stager can manage content at the database level as well as modules. Deployment appears to manage content at a higher level and can't update modules. There would be use cases for each.

The above was gleaned from simply reading the module pages.

This page should be editable

This page should be editable to all, so would be great if you could jump in and add what you mention above.

Done. I've yet to use any of

Done. I've yet to use any of these modules so can't comment any further.

Nice, thanks =D

Nice, thanks =D

Methods

There probably should also be a page on deployment methodologies, as these module are just tools, and this page provides no comparison of ways to use them. Also, there are plenty of other tools out there that aren't modules, like Capistrano, Git, Drush rsync, etc.

Here are some links, but perhaps we should start a new page too:
http://stackoverflow.com/questions/730138/whats-best-drupal-deployment-s...
http://opc.com.au/web-development/drupal-release-management-drush-and-git
http://groups.drupal.org/packaging-deployment
http://dcycleproject.org/faq

Nice work on the page

Nice work on the page cleanup! Agree with your suggestion, though want to research what is already up on drupal.org first as well.

Page status

About this page

Drupal version
Drupal 5.x, Drupal 6.x, Drupal 7.x
Audience
Site administrators

Site Building Guide

Drupal’s online documentation is © 2000-2013 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0. PHP code is distributed under the GNU General Public License. Comments on documentation pages are used to improve content and then deleted.