An approach I've seen is to use some sort of deployment script (Fabric, Ansible), etc... In there, you have a file with all of your "secrets" that is encrypted. This is checked in to source control. (But should still be private.) The person doing the deploy provides a pass phrase to decrypt the secrets at deployment time.
Chris On Thu, Feb 27, 2014 at 3:03 AM, Chris Withers <[email protected]>wrote: > Hi All, > > I'd like to source control my .ini configs, but they have a sqlalchemy url > in them which contains a username and password. > > Obviously, I don't want those in source control. > > What's the best practice for handling this situation? > > cheers, > > Chris > > -- > Simplistix - Content Management, Batch Processing & Python Consulting > - http://www.simplistix.co.uk > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
