Thursday, October 2, 2014

Re: Config: DB or git?

On Thu, Oct 2, 2014 at 12:21 PM, Thomas Güttler <hv@tbz-pariv.de> wrote:
> Am 01.10.2014 um 14:56 schrieb Collin Anderson:
>>
>> If you're a programmer or sysadmin, configuration should be done in files.
>> If you're not a programmer or sysadmin, it
>> should be done in the database.
>
>
> Why do you look the person for a decision like this?
>
> Wouldn't it be better to look at the data which gets configured here?
>
> I love git like most programmers love their version control system.
>
> But for most stuff config in DB is much better.
>
> example: INSTALLED_APPS
>
> Wouldn't it be really cool if you could add an app by pressing a button?
>

I have developed, maintained, managed and supported a generic ORM that
stores all details about how things are configured - models, fields,
classes, behaviours - in the DB for the past ten years, and I can tell
you that, no, it is not really cool, it is a massive pain in the
proverbial.

How your models and fields behave is not configuration it is code.
What models are part of a project is not configuration, it is code.
What folder a project is in, what credentials to connect to a
database, what proxy to talk to - these things are configuration.

They are all settings, but some settings are configuration, some
settings are part of your codebase. If you change what is in
INSTALLED_APPS, it is no longer the same project, but if you change
what DB server to connect to it is still the same project.

Cheers

Tom

--
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFHbX1LYS%3DeFpoM9BHiiGGi6ZY2-yGa%3D2itbjde%2BVj3YcwaBiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment