> > There's definitely no well supported way to do this, and a plugin > wouldn't > > really be the right approach for the reason Olemis mentioned > (chicken/egg). > > > > Considering that there's a real use case for this , question is : is > it a good idea to request for this enhancement by creating a ticket in > t.e.o issue tracker ?
Before I file a ticket, I'm actually wondering whether this database override is sufficient for Trac on Heroku. Since Trac (and plugins) are free to make persistent changes to the environment's trac.ini file and calling config.save(), what will happen to that file on a Heroku environment, since it will then have changes that are not committed to the repository that's managing it? I wonder if the entire Configuration implementation needs to be swappable -- so that e.g. a Heroku-friendly implementation could get and set *all* settings directly from os.environ (which is persistent on Heroku). From a quick grep, it looks like it wouldn't be very hard to make this swappable, since almost all usage of Configuration is through `env.config` instead of instantiating a `Configuration` directly. But maybe this isn't necessary, or maybe Drew's already figured out another approach that works for managing the Trac environment's config file. -Ethan -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/groups/opt_out.
