I have working copies of code in development on multiple places - work machine, home machine, laptop, etc. I can't always force these machines to use the same credentials; I end up with each machine having slightly different database.yml configurations. With Subversion-Pre-Capistrano, I left the entire config directory out of Subversion (or some kind of template; see http://subversion.tigris.org/faq.html#ignore-commit ). But Capistrano deploys the config directory to the server, so this trick becomes less useful. Is there a way around this?
on 2006-04-16 18:26
on 2006-04-16 18:45
You can have more than the basic 3 environments that the config system represents by default. So, you can have dev1, dev2, etc. That way you can keep config/ under control. -- -- Tom Mornini
on 2006-04-16 18:57
Perfect! Danke! -- Joshua