Monday, September 29, 2014

Re: Config: DB or git?

Den 29/09/2014 kl. 15.04 skrev Thomas Güttler <>:

> Hi,
> of course we separate data from code:
> - code belongs into version control (git)
> - data belongs into a database (postgres)
> But where does configuration belong?

Strictly speaking, configuration belongs in a configuration management system - Ansible, Chef and Puppet being just examples. The words option, setting, preference and configuration are often used interchangeably, but if you define "configuration" as "something that is loaded by the program on startup" and which is not universal for all installations, then you must store configuration independently from the VCS and DB.

Depending on your hosting environment, you could store your host-specific configuration in a versioned Fabric script. But keep in mind that storing cleartext passwords is bad practice, be it in a database or in Git.


You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

No comments:

Post a Comment