Hi,
il our case, we use SaltStack to deploy our pyramid apps.
The production.ini file is a jinja2 template.
The password is stored in the Pillar datas (confidential datas stored on
our supervision server).
Example :
In /srv/salt/pyramid_states.sls :
"""
/etc/app/production.ini:
file.managed:
- source: salt://etc/app/production.ini
- template: jinja
"""
In /srv/salt/etc/app/production.ini:
"""
...
sqlalchemy.url = mysql://dbuser:{{ pillar.get('sql_password',
'defaultpass') }}@localhost/dbname?charset=utf8
...
"""
In /srv/pillar/myserver.sls:
"""
sql_password='mystrangepassword'
"""
Regards
Le 27/02/2014 09:03, Chris Withers a écrit :
> 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
>
--
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 pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
