On 10/16/13, Ethan Jucovy <[email protected]> wrote: >> > 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. >
Well , it's possible to replace Configuration objects with whatever compatible class you could develop . Indeed product configuration in Apache™ Bloodhound is stored in the database (see multiproduct.config module ...) . In that case I initially proposed a mechanism to make config implementations swappable , but the complexity was not really considered useful for our use cases , especially considering that we had other priorities ... [...] -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- 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.
