Version control of own site

[kneehigh]

Is anybody using a version control/source control system for maintaining the codebase of their installed cms system ?

If so what ?  If you had your time over would you do it again - or try something different ? How well does it allow to synch with a prodn site ?

Tips, traps, advice etc ?

TIA
Kim

[monghidi]

Great question!

I occasionally make tweaks, edits, or changes to module or tags code, either to fix something that's a little bit broken, or to change slightly how something works, or to get around a particular limitation or quirk on my server. Then, when I am creating a new site from scratch, I have to try to remember everything I did on the previous one to bring it into a similar working state.

I think version control for my own edits would be great, but I too am wondering if anyone else does this, and how? I work locally and then upload to the live remote site, so tips on synching is important.

[tsw]

if you fix something why not publish your fix and have the problem solved for everybody???

and if you do a change that you think thats only suitable for you, think again. there could be multiple people out there just dying for that small change (even if there would be a setting to apply the change).

to answer your question just set up a svn server and put your site in there (you could even do dbdumps and commit them to have manual versioning of content...)

[kneehigh]

I must be psychic  - see the big blog post on git.

Our problem is now that we are live we still need to add some major functionality & don't want to put a bug fix in a file that has untested changes

[Pierre M.]

if you fix something why not publish your fix and have the problem solved for everybody???

yes, for everybody for ever. (so including you and your upgrades)

Pierre M.