On 10/16/13, Ethan Jucovy <[email protected]> wrote: > On Tue, Oct 15, 2013 at 11:44 PM, Drew Carey Buglione < > [email protected]> wrote: > >> My reason for desiring to do things this way is simple: I'm running Trac >> on Heroku, where there is a convention of keeping all private or >> environment-specific data in config variables. >> >> I can not deploy any files to Heroku without checking them into version >> control, and I'd like to avoid checking my database string into version >> control. >> >> Heroku provides the database string as an environmental variable, though, >> so if anyone has any idea how I can go about resolving my problem the way >> I'd like to, I'd really appreciate some pointers. >> > > 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 ? [...] -- 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.
