Maintaining multiple catalogs on different machines

[bw38]

I have a Mac Mini running 10.7 and my main iMac running 10.6. Naturally I’m making different changes to catalogs to maintain images for both OSes. The problem I’m running into is that while I edit catalog files on the Mac Mini, I sometimes forget to put them on my iMac (and vice versa). So far what I’m doing is just opening up a shared folder and dropping the files I create onto my iMac (and vice versa). This way files remain in sync.

But I’m thinking, there’s got to be an easier way to handle this. I was thinking perhaps I could setup an svn, but I’ve never done that. I could literally just edit the catalog files, upload them to the server running the svn, and then just update any machine using svn. At least, that’s my basic understanding of how svn works. Correct me if I’m wrong.

The other option is to go full throttle into 10.7 and stop using 10.6 on a day to day basis. But I still like to keep a fresh (and somewhat updated) image for 10.6.

What would you recommend when dealing with multiple catalogs on different machines?

[Arjen]

svn (or another vcs) is a good option as it also gives you the opportunity to revert to a previous version of your catalogs.

I host all my catalogs and packages on a web server and also a simple script that gets all the resources from the web server and builds an image.
Converting a workstation to a buildstation is just a oneliner:

[code]curl http://mywebserver/path/to/buildscript.sh | sudo sh[/code]

I was planning to share my setup with the world but I didn’t have time to create a nice writeup.

[Author]

Posts