Hi Ryan, For my vhost.conf files I have a vhost.conf.tmpl file in my repo and an svn:ignore property for vhost.conf. When you check the code out on a new machine you just copy the template file to vhost.conf and you change that.
Good luck, Marijn On Jul 1, 2009, at 12:29 PM, Ryan wrote: > > So I have a project, with 4 config files that need to be modified for > each machine the project is checked-out to. > Said config files are in the repository as templates ie the structure > is there but the actual config values are not set. > > I checkout the project and then need to modify the config files to run > on my machine, but I do not want to update the repo with my particular > flavour of the config files, I want the ones in the repo to remain > with their template values. > > The only options I see using Versions is to _not_ run the commit on > these files... but this is driving me and my OCD nuts as there are > little numbers indicating "you have updated these files". > Or > Of course each developer could commit the updates to these files and > everyone could be sure just to checkout the templates at revision one. > > But neither of these seems particularly "nice". > Perhaps I am missing something, can anyone advise? > > Ryan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
