You are here

Home » API reference » Deploy - Content Staging 7.3

README.txt in Deploy - Content Staging 7.3

Same filename and directory in other branches
  1. 5 README.txt
  2. 6 README.txt
  3. 7.2 README.txt
ABOUT DEPLOY
------------

The Deploy module is used to deploy Drupal content to other Drupal sites or
arbritary systems. Two concrete use cases are:

 * using it as a content staging solution
 * usgin it to push content downstream from a main site to several sub sites

The provided workflow for working with deployments is very flexible. You can
have different workflows for deploying different kinds of content on your site.
Those different workflows are defined by different "plans". One plan deploys
content to one or many "endpoints". One endpoint usually represents a site or
an arbritary system.

Content that should be deployed can automatically be filtered by a view or
picked manually by an administrator. The aggregated content can be processed
instantly on one page request or visually by the Batch API with a progress bar.
Content can be deployed to endpoints through services as an REST API, XML-RPC
calls or exposed as a Atom feed that clients can subscribe to. HTTP basic
authentication is the default authentication method. Other methods can be
added via contrib modules or by writing custom plugins.

Deployment of plans can be triggered in many different ways. Either manually by
an end user, by a custom Rules event or through a Drush command.

File

README.txt
View source 
  1. 

  2. ABOUT DEPLOY

  3. ------------

  4. 

  5. The Deploy module is used to deploy Drupal content to other Drupal sites or

  6. arbritary systems. Two concrete use cases are:

  7. 

  8.  * using it as a content staging solution

  9.  * usgin it to push content downstream from a main site to several sub sites

  10. 

  11. The provided workflow for working with deployments is very flexible. You can

  12. have different workflows for deploying different kinds of content on your site.

  13. Those different workflows are defined by different "plans". One plan deploys

  14. content to one or many "endpoints". One endpoint usually represents a site or

  15. an arbritary system.

  16. 

  17. Content that should be deployed can automatically be filtered by a view or

  18. picked manually by an administrator. The aggregated content can be processed

  19. instantly on one page request or visually by the Batch API with a progress bar.

  20. Content can be deployed to endpoints through services as an REST API, XML-RPC

  21. calls or exposed as a Atom feed that clients can subscribe to. HTTP basic

  22. authentication is the default authentication method. Other methods can be

  23. added via contrib modules or by writing custom plugins.

  24. 

  25. Deployment of plans can be triggered in many different ways. Either manually by

  26. an end user, by a custom Rules event or through a Drush command.

  27.