I am wondering how people roll out deployment processes when you must retain content on downstream systems.
For example, I have my local dev space, and then there is also the public site. What are some way people handle deployments?
Ideas:
- Roll out new files, schema & data, with exclusions to leave content on prod untouched. Does anyone have a thorough list for this process type? [list][li]My current plan for this option would be ignore the tables:[list] [li]modx_manager_log
- modx_session
- site_content_metatags
- site_tmplvar_contentvalues
- site_content
- my folder(s) for user content uploads (files)
[/li] [/list][/li]
[li]This should be sufficient for me, because for everything else (chunks, snippets, template variables) my development version is the reference[/li]
[li]The only other thing that occurs to me is that I would need to compare the ignored tables for schema changes[/li]
[li]
Pull down all current info from prod, and then push it all out with no exclusions. This is not usually the way to go, as content on prod may be constantly changing, and so would require a content freeze, and has space for error because you are moving the actual content. Also It’s a pain in the neck, why move twice when you could just leave the content in place.[/li]
[/list]
I looked into pulling the content back using provisioner, but this does not seem to be a thorough solution, and I thought Packman could be the way, but that isn’t for resources.
Going to start testing this today. Thoughts? Looking forward to hearing how other people do this, and/or writing the book on it
PS this is for Revo 2.0.4+
