Content master
Component ID
1823716
Component name
Content master
Component type
module
Maintenance status
Development status
Component security advisory coverage
not-covered
Component created
Component changed
Component body
Content migration is always a pain with drupal. You can try feeds or migrate module but for me they take far to long. This approach follows the rule that only one database has content added to it (the content master) and all other databases are slaves. Using Amazon s3 we can push and pull database and file changes very quickly and avoid content migration.
If you wish to have content in staging which one data you export just the content to live this isnt the module for you.
If you want to have all content on one database and have a slick simple way from a slave database, to say "get me the latest content db" then this module is for you.