|
Tuesday 26 August 2008 4:07:42 pm
Hi Jorge, When I read your question I immediately thought "Versioning System". Something like SVN (http://subversion.tigris.org/). However, the seeming lack of a network might be a bit of an issue and make things a bit clumsy: Given that data from each PC needs to be exported and saved to some 3rd party storage medium anyway (CD-R, USB or External HDD etc) in order to later "merge" it to (presumably) the "master" install, could you not install SVN and an SVN repository on each client PC, then check-in changes from that eZ Install, on that PC, into that PCs local repository as an SVN branch? Then you could save the SVN working copy (and obviously all the files in the .svn dir) to your storage medium and then once connected to the master PC, run an SVN merge from each client PC's stored repository files and data, with the master install's SVN data. I have to concede however that setting up SVN to do this might require some effort (ensuring repository names, URLs and directory hierarchies were identical across each client PC - hard - but not impossible) and also that merging so many branches might become very difficult and the potential for merge conflicts will increase. I might add I'm no SVN expert, I have never tried anything like this - I just thought of it just now :-) but maybe something to consider? Maybe ask around at the SubVersion website mailing list or IRC (Look under "Help" at http://subversion.tigris.org/) You can't be the first person to have posed this scenario, surely? :-)
Good luck,
Russ
Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom
Believe nothing, consider everything.
|
