On Tuesday, 5 March 2013 13:35:41 UTC, Dave Murphy wrote: > > On Tuesday, March 5, 2013 1:17:13 PM UTC, Michael wrote: >> >> Are there other better options that wouldn't force people to change their >> code to use the charm? >> > > For the charm to be of sufficient value, it needs to be opinionated, > otherwise it's going to suffer from trying to work out-of-the-box for > everyone. >
True but using environment variables only moves the problem somewhere else: it means that you still need to auto-generate the part of the startup script that sets the environment variables. Besides, as said above, it would force django app developers to explicitly use those environment variables and if they forget one of misspell it, the danger is that it would fail silently. Then the risk is that it's hard to debug because you're hunting setting values in two places: the django settings and the startup scripts that sets the environment variables. So I'd much rather have the charm auto-generate part of the config in a sensible way and then tell people: if you use Juju, don't provide those settings in your config, the charm will do it. Bruno -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
