Hi Chris,
we're using buildout for our setups here and are generating the config
files using collective.recipe.template. Now the usernames, passwords and
other dynamic elements are in buildout.cfg - no advantage so far.
But: We are using a base.cfg and then inheriting dev.cfg, rc.cfg and
live.cfg from it. On the actual server we're creating a minimal (few
lines) non-version controlled buildout.cfg, just inheriting from one of
the three targets flavors, and putting the password in there.
I hope there we're a simpler solution, but its works fine anyway.
regards Jens
On 2014-02-27 09:03, Chris Withers 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
--
Klein & Partner KG, member of BlueDynamics Alliance
--
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.
