On Wed, Oct 16, 2013 at 3:34 PM, Drew Carey Buglione < [email protected]> wrote:
> So, I gave up on doing things within Trac, and combined the two approaches > suggested earlier. My setup is documented here: > https://github.com/drewbug/heroku-trac#protect-database-string > This is really cool, thanks for sharing it. > As for changes to the configuration file not persisting: I'm not too > worried at the moment, but I'm not exactly able to come up with an idea on > what the worst-case scenario would be. Ideas? > Well .. changing which plugins/components are active through the web interface is probably the biggest // most likely problem. If you do change that through the web UI and then Heroku decides to wipe out your changes, I guess you could conceivably end up with a broken site, or at least one that does not behave at all how you expect it to. A couple of other (probably minor) things that can be changed TTW and therefore might reset unexpectedly would be the project name, url, default timezone and language, and logging configuration. The other thing that seems both likely and major (at least from my own usage) would be custom ticket fields or ticket workflow changes, but those are both only editable through the web via plugins (CustomFieldAdminPlugin and TracWorkflowAdminPlugin) so if you don't have those installed you're probably pretty OK. Similarly if you have IniAdminPlugin installed all bets are off. And of course it's hard to pin down exactly what through-the-web edits will result in config changes once you get into plugin-land. -- 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.
