5

My Question is there any way we can track the node changes on Staging Server and Push the same to the Production Server. Best use case will be,

  • Customer does not want to change the content on Production server.
  • He wants to first change on Staging server get it tested and push the content to live server.
  • Have revisions for changes so that he can revert back any time using node re- visioning system !

Can we do this maintaining the node id's same across staging and live servers ? Is there any out of the box solution for this like feature module does for configuration changes tracked using modules?

Improve this question
1

2 Answers 2

Reset to default
3

For Node changes, you can use node export module to migrate node between drupal installations. for Tracking Configurations changes there is another module configurations , i haven't tried yet. Be sure cos the module release is still in dev

Improve this answer
2
  • I don't think node export will track node id's between different environments! It will just help to export import content. And does, it solve content update problem from staging to production ?
    – Anil Sagar
    Oct 5, 2012 at 11:39
  • 3
    node_export leverages the UUID module so nids can be different between systems.
    – mpdonadio ♦
    Oct 5, 2012 at 11:54
2

Helpful conversation here.

You could also check the Deploy module

The Deploy module is designed to allow developers to easily stage Drupal content from one site to another. Deploy automatically manages dependencies between objects (like node references). It is designed to have a rich API which can be easily extended to be used in a variety of situations.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.