You are here

Home » API reference » Deploy - Content Staging 6

README.txt in Deploy - Content Staging 6

Same filename in this branch
  1. 6 README.txt
  2. 6 modules/content_copy_deploy/README.txt
Same filename and directory in other branches
  1. 5 README.txt
  2. 7.3 README.txt
  3. 7.2 README.txt
NOTE: This module is currently in an alpha state, and many aspects of it remain 
in the proof-of-concept realm. Please do not use it for any production purposes 
until such a time as a 1.0 is released.

The deployment framework is a series of modules which are designed to allow 
developers to easily stage Drupal data from one site to another. It is designed 
to have three parts that work together:

* Deployment API - This implements the concept of a deployment plan. You create 
a deployment plan and add objects to it which will be deployed (content types, 
views, etc.) When the time comes these items are pushed to a server you specify 
via XMLRPC with an API key. The data stored about each item is extremely minimal, 
relying largely on the implementers to implement object-specific knowledge. 
Currently this is deploy.module

* Deployment Implementers - Individual modules implement the deployment API to 
add the data they need to a deployment plan, and expose that ability to the front 
end. Currently I have content_copy_deploy.module and system_settings_deploy.module.

* Deployment Services - Services modules which contain the knowledge to receive 
deployed data and do what is appropriate on the destination server. Currently I 
have content_copy_service.module and system_settings_service.module. 

Installation and usage instructions can be found in INSTALL.txt

File

README.txt
View source 
  1. NOTE: This module is currently in an alpha state, and many aspects of it remain 

  2. in the proof-of-concept realm. Please do not use it for any production purposes 

  3. until such a time as a 1.0 is released.

  4. 

  5. The deployment framework is a series of modules which are designed to allow 

  6. developers to easily stage Drupal data from one site to another. It is designed 

  7. to have three parts that work together:

  8. 

  9. * Deployment API - This implements the concept of a deployment plan. You create 

  10. a deployment plan and add objects to it which will be deployed (content types, 

  11. views, etc.) When the time comes these items are pushed to a server you specify 

  12. via XMLRPC with an API key. The data stored about each item is extremely minimal, 

  13. relying largely on the implementers to implement object-specific knowledge. 

  14. Currently this is deploy.module

  15. 

  16. * Deployment Implementers - Individual modules implement the deployment API to 

  17. add the data they need to a deployment plan, and expose that ability to the front 

  18. end. Currently I have content_copy_deploy.module and system_settings_deploy.module.

  19. 

  20. * Deployment Services - Services modules which contain the knowledge to receive 

  21. deployed data and do what is appropriate on the destination server. Currently I 

  22. have content_copy_service.module and system_settings_service.module. 

  23. 

  24. Installation and usage instructions can be found in INSTALL.txt

  25.