I know that people have asked this two or three billion times, but I have to ask because I keep seeing people mention that MODx is a pain with version control because of what it stores in the database.
So what gives? Is MODx really that difficult to set up with version control (Git in this case).
Cheers!
This issue has troubled us all... and seems it’ll be addressed in 2.1 (at least from the forums chatter).
IMHO, the best practice today would be to do as much as possible coding to be packaged for transport (i.e. addons)
This way, you could have your own core code in the svn. then once in a while you run your build batch that exports from the svn, builds the package, and you’re ready to "upgrade/reinstall" via the package management.
So, yea... it only resolves the adddon business, and the "old school evo-style" way of working with the manager to build the site, stay out of the svn.
Simpler way - you could also add the whole site’s folder into svn, then work directly in the components/yourStuff folders (without packages), and do all your chunks/snippets in files. but still - the database is out of the svn.
good luck
Theres also this in the pipeline
http://modxcms.com/forums/index.php/topic,40916.msg257149.html, if your on linux it helps, integration with SVN is now done, not tried it with GIT but hopefully it should work.
Use MODx, or the cat gets it!
-
☆ A M B ☆
- 427 Posts
I just listened to Linus Tolvalds discussion on Git at Google -- I was impressed.
I mean who else could tell Google they were stupid and get applause?
http://www.youtube.com/watch?v=4XpnKHJAok8
I am running Fedora Core 12, so I will install it as it is in the repo...
