Adrian Holovaty wrote:
>So the question is, do we give the generated settings.py file all the
>possible settings, or does it continue to have just the settings that
>are commonly changed? I really could go either way on this.
>
>
It's good that current settings.py looks small. This adds to the
Those who've also setup Apache a million times will also recognize this
approach...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@g
On 2/18/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> So the question is, do we give the generated settings.py file all the
> possible settings, or does it continue to have just the settings that
> are commonly changed? I really could go either way on this.
Personally, I like the idea of setti
On 2/17/06, pbx <[EMAIL PROTECTED]> wrote:
> That got me thinking: How about annotating the default settings file to
> describe all available settings? I'm talking about something along the
> lines of Apache's default httpd.conf.
Note that django/conf/global_settings.py holds the default values f
Luke wrote:
> One of the problems with an annotated conf file is what happens at
> upgrade time, when new config options have been added to the system.
> In the case of httpd.conf, it's not too bad for me because dconf
> (Debian conf system) is great and asks me what to do (i.e. doesn't
> overwri
Yeah. Postfix also has the nifty "postconf -n" command which shows you
*only* the settings that differ from the defaults (very helpful when
asking someone else for troubleshooting advice).
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On Friday 17 February 2006 16:40, pbx wrote:
> That got me thinking: How about annotating the default settings file
> to describe all available settings? I'm talking about something along
> the lines of Apache's default httpd.conf.
> So, reasonable people, what do you think?
One of the problems
It is a nice touch to have -- Postfix's main conf file is so nicely
commented you can just about completely configure and run it just by
reading the conf file (well, for small setups at least).
--~--~-~--~~~---~--~~
You received this message because you are subscr
No -- I mean that the generated settings.py file itself would have
descriptions of each setting, including the defaults. See the
bogofilter link.
pb
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develope
On Feb 17, 2006, at 10:40 AM, pbx wrote:
> That got me thinking: How about annotating the default settings
> file to
> describe all available settings? I'm talking about something along the
> lines of Apache's default httpd.conf.
You mean something like http://www.djangoproject.com/documentatio
I made a couple dumb settings.py mistakes this morning (e,g, confusing
DEFAULT_FROM_EMAIL with SERVER_EMAIL).
That got me thinking: How about annotating the default settings file to
describe all available settings? I'm talking about something along the
lines of Apache's default httpd.conf.
I als
Thanks Ian. Is there a plan for the development of this sort of widget
as part of dojo in general that you are aware of that could fit into django?
Regards,
David
Ian Holsman wrote:
> http://turboajax.com/turbowidgets/ might be of interestest.
>
> BTW. they are about $200 for commerical use.
>
12 matches
Mail list logo
