Nice solution. I have found a way though. I have sensitive information in other files as well. So before update_code I run a git diff > shared_path/ xxxx.diff to keep modified info at hand, and then after deploy:symlink I apply the patch to the updated code. That way I always have in- server modified files as they were in the beginning.
On Jan 20, 2009, at 11:18 PM, Donovan Bray wrote: > > I keep a template of the database.yml marked up with erb with the > deploy scripts. I have an authentication.rb that is not in revision > control (a template is). My stage files use the settings from > authentication.rb and a task deploys the final database.yml after > update_code. In this way no sensitive settings are exposed by a > checkout, devs are free to customize their deploys to their test > servers, and ops maintains tight control over the production > authentication.rb values. > > On Jan 19, 2009, at 11:27 PM, Andres Rodriguez <[email protected]> > wrote: > >> >> Hi, since I have multiple apps of the same type deployed to different >> servers I have a specific version of files database.yml in each >> deploy. >> >> The normal way to save these files would be to use git stash and then >> git stash apply after checking out new code. >> >> Is there a way to do this with capistrano? I haven't found a way yet. >> >> Thanks for any help. >> >>> > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
