Re: dbsettings, and user configurable app settings

This was the initial question: On Feb 26, 8:11 am, Jared Forsyth wrote: > I have been looking around for a way of managing user-configurable > application settings In this discussion we must IMHO different between "low-level settings", "admin configurable settings" and "user configurable settin

Re: dbsettings, and user configurable app settings

On Wed, Mar 10, 2010 at 6:31 PM, Matt Boersma wrote: > On Wed, Mar 10, 2010 at 7:51 AM, Brian Rosner wrote: >> >> On Mar 10, 2010, at 7:16 AM, Joan Miller wrote: >> >>> It's a disaster from the maintenance view point. If it were not so, >>> then people would not be proposing to refactor the setti

Re: dbsettings, and user configurable app settings

is there a different > generally accepted method for having user-friendly app settings? (e.g. don't > require code modification) > > I think that this idea is pretty essential to django's ease of use; there > are many applications which have (or should have) settings which o

Re: dbsettings, and user configurable app settings

On Wed, Mar 10, 2010 at 7:51 AM, Brian Rosner wrote: > > On Mar 10, 2010, at 7:16 AM, Joan Miller wrote: > >> It's a disaster from the maintenance view point. If it were not so, >> then people would not be proposing to refactor the settings as has >> been made in Pinax, or from multiple posts so m

Re: dbsettings, and user configurable app settings

As far as a solution that "magically solves everyone's problem nicely", that's what django-appsettingsis trying to be :). It handles quite nicely the issues of scoping and maintainability that you discussed, organizing everything in a pythonic manner.

Re: dbsettings, and user configurable app settings

On Mar 10, 2010, at 7:16 AM, Joan Miller wrote: > It's a disaster from the maintenance view point. If it were not so, > then people would not be proposing to refactor the settings as has > been made in Pinax, or from multiple posts so many times. Like I mentioned in the post you made to the pina

Re: dbsettings, and user configurable app settings

On Wed, Mar 10, 2010 at 10:16 PM, Joan Miller wrote: > It's a disaster from the maintenance view point. If it were not so, > then people would not be proposing to refactor the settings as has > been made in Pinax, or from multiple posts so many times. > > This is nothing new. Many people dislikes

Re: dbsettings, and user configurable app settings

1) In implementation, how is a YAML configuration file any different than the Java/XML example that you offered? Syntactical differences between XML and YAML aside, both systems define settings in markup languages (which by definition have minimal capability for logic) that are eventually parsed (b

Re: dbsettings, and user configurable app settings

I really don't see how your YAML file is any more maintainable than Django's settings.py approach? If anything, I would argue that it is less maintainable, as you would have to maintain not only your YAML files moving forward, but also the code which transposes it into a settings.py. On Wed, Mar 1

Re: dbsettings, and user configurable app settings

It's a disaster from the maintenance view point. If it were not so, then people would not be proposing to refactor the settings as has been made in Pinax, or from multiple posts so many times. This is nothing new. Many people dislikes that kind of configuration, of the same that many people hates

Re: dbsettings, and user configurable app settings

On Wed, Mar 10, 2010 at 6:18 PM, Joan Miller wrote: > Whatever configuration system using variables of a language is a > disaster and it's going not maintainable as has been showed in Django. That's a pretty wild assertion to make without any evidence, and it's completely contrary to my personal

Re: dbsettings, and user configurable app settings

ere a different > generally accepted method for having user-friendly app settings? (e.g. don't > require code modification) > > I think that this idea is pretty essential to django's ease of use; there > are many applications which have (or should have) settings which only ef

Re: dbsettings, and user configurable app settings

> > a) project settings (settings that affect the installation, etc... > > this can include automatic install of dependencies, etc... but > > normally do not change, this could be done in a similar script ) > > b) app settings (settings that change once and while, but t

Re: dbsettings, and user configurable app settings

on, etc... > this can include automatic install of dependencies, etc... but > normally do not change, this could be done in a similar script ) > b) app settings (settings that change once and while, but that are > meant to be changed by a superuser, or admin) > c) user settings

Re: dbsettings, and user configurable app settings

ld be done in a similar script ) b) app settings (settings that change once and while, but that are meant to be changed by a superuser, or admin) c) user settings (settings that are to be set and changed by a user himself, that could be changed in a "profile app") more to come, now i

Re: dbsettings, and user configurable app settings

I think there are some settings which are for the developer, and some which are appropriate for an admin user, who is not necessarily the developer, to have access to. In addition, there are some settings which should be modifiable without necessitating a server restart. There is value in having co

Re: dbsettings, and user configurable app settings

I don't think that settings are for users. They are for the developer. The type of settings you are looking for really should be set up as part of your application. Users can't choose a DB password or your server's time zone, or which apps are installed. If you're creating an SAAS you'd be better t

Re: dbsettings, and user configurable app settings

For PyLucid i have made http://code.google.com/p/django-dbpreferences/ """ A django app defines a form with initial values. The form cleaned data dict would be stored serialized into the database. The app can easy get the current preference dict and the user can easy edit the values in the django

Re: dbsettings, and user configurable app settings

I'm currently working on a solution to this which I call appsettings, and I think it addresses many of the concerns raised here. appsettings loads your module's settings.py in much the same way that contrib.admin loads your admin.py, and you call appsettings.register (can be used as a decorator) to

Re: dbsettings, and user configurable app settings

On Mar 1, 9:40 am, stuff4ash wrote: > I am not necesary advocating magic. But the need for a more robust (or > lets say, any) configuration management exists for many. "Configuration management" is a fuzzy phrase that can mean many things to many people. I think it'd be more helpful to focus on s

Re: dbsettings, and user configurable app settings

> I've never understood the desire for more magical behavior here. My > apps have a settings.py that imports django.conf.settings and provides > any necessary defaults for unset settings; the rest of my app imports > from there. Works great, easy to look and see what settings my app > consumes and

Re: dbsettings, and user configurable app settings

On Feb 27, 1:53 pm, stuff4ash wrote: > b) easy way to register, override, configurations for apps. > a settings.py in an app folder that is "magically" loaded the same way > other things are would suffice, but there has to be a way to: I've never understood the desire for more magical behavior

Re: dbsettings, and user configurable app settings

ace to apply some development if > > anyone is interested in working towards better settings management. > > >http://groups.google.com/group/pinax-core-dev/browse_thread/thread/d9... > > > -Wes > > > On Feb 26, 2:11 am, Jared Forsyth wrote: > > > I have been looking ar

Re: dbsettings, and user configurable app settings

ply some development if > > anyone is interested in working towards better settings management. > > >http://groups.google.com/group/pinax-core-dev/browse_thread/thread/d9... > > > -Wes > > > On Feb 26, 2:11 am, Jared Forsyth wrote: > > > I have bee

Re: dbsettings, and user configurable app settings

gt; On Feb 26, 2:11 am, Jared Forsyth wrote: > > I have been looking around for a way of managing user-configurable > > application settings, and the only solution I have found is dbsettings, > > which looks like it hasn't been touched in 3 years. > > So, I would like to know: is

Re: dbsettings, and user configurable app settings

n looking around for a way of managing user-configurable > application settings, and the only solution I have found is dbsettings, > which looks like it hasn't been touched in 3 years. > So, I would like to know: is dbsettings dead? Or is there a different > generally accepted me

dbsettings, and user configurable app settings

aving user-friendly app settings? (e.g. don't require code modification) I think that this idea is pretty essential to django's ease of use; there are many applications which have (or should have) settings which only effect UI or minor behavioral issues, and shouldn't require a serv

App settings

Whenever the app objects discussion is resuscitated, the following by yours truly may be of relevance: http://github.com/mrts/plugit/tree/master As of now, settings handling is present. The SettingsUpdater class in plugit/settingshandler.py provides a high-level API for updating configuration fi

Re: [Pony] Per app settings

On Thu, 2008-10-23 at 10:29 -0700, shabda.raaj wrote: > My project is, > > project/ >blog/ >forum/ >wiki/ >setting.py > > Now so all my views from blog/ must have the Blog object, all views > from forum should have Forum object, all views from wiki should have > Wiki object. >

Re: [Pony] Per app settings

On Thu, Oct 23, 2008 at 1:29 PM, shabda.raaj <[EMAIL PROTECTED]> wrote: > > I was doing a little research and saw #5049, which was closed as > WONTFIX by Russell, but I cant seem to find the referenced discussion, > and am posting this as maybe this proposal is significantly different > than what

[Pony] Per app settings

My project is, project/ blog/ forum/ wiki/ setting.py Now so all my views from blog/ must have the Blog object, all views from forum should have Forum object, all views from wiki should have Wiki object. So in settings.py I can have TEMPLATE_CONTEXT_PROCESSORS = ( 'wiki_contextpro