Incremental Deploy

This project is not covered by Drupal’s security advisory policy.

Incremental Deploy is built on top of Deploy module. In conjunction with Services module, Deploy makes it possible to package up content such as nodes, users and taxonomy terms, and send them via XMLRPC calls to a remote Drupal site.

With Deploy module, in order to deploy a piece of content, it must be added to a plan (though it is possible to batch deploy nodes from the content administration page). With Incremental Deploy, the idea is that changes automatically get scheduled for deployment to the target environment as soon as they are made in the source environment. So, every time a variable is changed, or a node is updated or the contents of a node queue are re-arranged, these changes will show up in the current "active" deployment plan, ready to be pushed to the next stage in the chain.

The main module looks after deployment of core entities, such as nodes, blocks and variables, while other items are dealt with in submodules. The submodules available at present are:

  • Nodequeue Deploy Allows for the deployment of the contents of an individual subqueue
  • Flag Deploy Allows for the deployment of global flaggings of nodes, users and comments
  • Nodewords Deploy Allows for the deployment of meta tags

The relevant services for all extra items (i.e. where not provided by Services module itself) are split between incdep_service module (for core entities) and incdep_services_extra for everything else.

Dependencies:

Notes:

  • Nodequeue deployment relies on machine names for node queues. These exist as yet only in the 6.x-2.x-dev release of Nodequeue module.

Project information

Releases