On Wednesday, October 1, 2014 9:30:24 AM UTC-4, Collin Anderson wrote: > > If you're not a programmer or sysadmin, it should be done in the >> > database. >> > > Basically if only users are configuring things (who don't know how to use > revision control), then I think it makes sense to have it in the database. >
I don't think your claim holds true for larger projects or at organizations that have more business processes. At my current company, the configuration for the service must be in a database (DynamoDB) to allow for centralized management, auditing, and the ability to change the configuration without a deployment or service restart. Regards, Michael Manfre -- 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+unsubscr...@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/c2a810e0-0edd-4d1a-85c7-e5022559fb0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
