Re: [mezzanine-users] Using local_settings.py is awkward - here is a better way.

I've not had any problems with the workaround. I think the mezzanine set_dynamic_settings should be phased out completely so that users can adopt any reasonable settings policy they like. If there are really things that mezzanine needs to do to edit the settings, it should do them by editing the s

Re: [mezzanine-users] Using local_settings.py is awkward - here is a better way.

I’ve been thinking about this for quite some time personally. The *local_settings.py* approach does lead to some unpleasant quirks sometimes, and the multi-settings-file approach Paul mentioned is being advocated by many lately, including PyDanny (in his Two Scoops of Django

Re: [mezzanine-users] Using local_settings.py is awkward - here is a better way.

No worries, it's why we have user groups ;) Give the 'two scoops' (I don't know if they came up with it - it is where I read about it originally) settings folder method a try sometime. It is very effective and you can always have a secrets.py settings file in the settings folder excluded from the

Re: [mezzanine-users] Using local_settings.py is awkward - here is a better way.

Maybe I was the one who didn't quite understand ;) Apologies if I jumped the gun with my comments. On Wed, May 28, 2014 at 4:24 PM, Paul Whipp wrote: > Thanks for the feedback Josh, I enjoy Django and am enjoying my increasing > familiarity with Mezzanine. After rebuilding my own > website

Re: [mezzanine-users] Using local_settings.py is awkward - here is a better way.

Thanks for the feedback Josh, I enjoy Django and am enjoying my increasing familiarity with Mezzanine. After rebuilding my own websitewith it, I've now created and deployed four client sites on Mezzanine so far. INSTALLED_APPS is not in scope in local_settings.py so

Re: [mezzanine-users] Using local_settings.py is awkward - here is a better way.

Hey Paul, it seems like you don't quite understand how local_settings.py works. A project's settings.py imports local_settings.py allowing you to override settings as you like. For example, in local_settings.py you could put: INSTALLED_APPS += ("debug_toolbar",) just like you want. Also, leavi

[mezzanine-users] Using local_settings.py is awkward - here is a better way.

Having the local_settings always outside of version control is a pain on large projects and not being able to arbitrarily alter settings (rather than simply overwrite them) is agony. In 'normal' Django, the 'two scoops' method can easily be used to replace the local_settings.py import but in Me