Hello,
I am relatively new to modx. I was wondering what the easiest way is to rollout code related modx changes (e.g. snippets, templates, template vars, modules, etc) from a developer environment to a production environment where the customer is continually updating content. I cannot simply do a full DB export to production, as it would overwrite content changes made by the customer (i.e. updating the content of a document). Is there an easy way to identify which modx tables store code and which ones store content? Knowing this, I figure I could simply export the tables that store code and not overwrite content changes made by the customer.
Better yet, is there an online document/forum where methodologies and procedures are discussed concerning the build->test->debug->deploy lifecycle of a code change in modx? Having code stored in the database vs. on the file system is a new concept for me. Repositories like subversion cannot be used to track changes made to snippits and such. Consequently, rolling out code changes to production does not simply involved copying all changed code artifacts on the file system (e.g. php, js, and css files).
What do you modx veterans normally do?
Many thanks for your thoughts,
-Nathan
-
MODX Staff
- 10,725 Posts
For now, I typically keep all of my code on the file system in php files, and when I create snippets, they simply return the content from, or just simply perform, an include or include_once of the code file, as appropriate. I then use FTP or SVN to update the code portions.
