![]() |
|
|
|
|
Issue Type:
|
![Task]() Task
|
|
Affects Versions:
|
4.4.3 |
|
Assignee:
|
Unassigned |
|
Created:
|
21/Mar/13 5:29 PM
|
|
Description:
|
We have a quite large installation at rewe.de an I wonder if there are any known best practices how we could sync content (website/dms repos) from live to stage to dev. we usually develop contents on stage and move the final content with the live deployment to live. over the time stage grows out of sync with live. so what we would like to do is: after go live, sync back the live site to stage (and eventually even back to dev) making a complete backup is quite time and resource consuming (around 25Gig) and would mean to reset the stage db and taking down the site until restore is complete.
So I would love to hear what known best practices are around to achieve such a workflow.
|
|
Environment:
|
linux/magnolia 4.4.3
|
|
Project:
|
Magnolia
|
|
Priority:
|
![Neutral]() Neutral
|
|
Reporter:
|
Thomas Kratz
|
|
Security Level:
|
Public |
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
