On 27 Feb 2014, at 9:03, Chris Withers wrote:

> 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?

Production configuration doesn’t belong into the same repo like source code.

You’ll want to look into something like Ansible, Salt, Puppet, or Chef (I’d 
suggest to start with Ansible, it’s the easiest to learn and use but YMMV).

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to