Re: [PhillyOnRails] SVN question

[Cliff Moon <cliff@moonpolysoft.com>]

+1 for keeping sensitive config on the prod server(s) and telling 
capistrano to symlink them in during deployment.

PS:  hello from sunny California!

Mat Schaffer wrote:
> On Oct 5, 2007, at 9:38 PM, Walter Lee Davis wrote:
> > I am just getting started with svn, and one thing that wondered as I 
> > am pondering the import of a gigantic project is what can I do to 
> > keep people from seeing the password to my server when it appears in 
> > my conf files? How do you keep something in version control, yet have 
> > sensitive information redacted at the same time?
>
> As for keeping sensitive information version controlled, you could 
> consider a separate repository.  But in terms of handling things like 
> database config files that are going to change from server to server 
> you might want to take a look at the advice here:
>
> http://subversion.tigris.org/faq.html#ignore-commit
>
> You could potentially keep the production files under version control 
> in a separate repository, then pull them in as part of the deployment 
> procedure.  But I think for most people, a version-controlled template 
> does the trick.  Kinda like what Randy said.
> -Mat
> _______________________________________________
> To unsubscribe or change your settings, visit:
> http://lists.phillyonrails.org/mailman/listinfo/talk

_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk