This is probably a small design flaw. We're populating these settings in the
SiteConfiguration entry in the database with whatever was in settings.py,
settings_local.py or Django's default settings file, but that gives users no
way to override in settings_local.py.
Since we are populating it, we're going to need to provide equivalent
settings in the admin UI. If you can file a bug on what exactly you need to
change (cache backend and whatever else), I'll get to it soon.
Christian Hammond - [EMAIL PROTECTED]
On Thu, Oct 16, 2008 at 6:32 AM, eyal <[EMAIL PROTECTED]> wrote:
> I've got a question about how djblets.siteconfig handles changes in
> the settings.py and settings_local.py files.
> After upgrading to r1537 (and introducing djblets.siteconfig), as I
> understand, a SiteConfiguration object has been created (and stored in
> the db) that reflects the existing state of settings.py and
> If I later make changes to settings_local.py (for example, changing
> the cache backend), it's not reflected in the SiteConfiguration
> object, and ReviewBoard never sees this change. There also doesn't
> seem to be an easy way to update this field (the settings admin
> interface doesn't include it).
> This shouldn't be this cumbersome. I get a feeling that I missed
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at