I think Craig's approach is a good one (I'll have to try that out with my next Trac setup).
Even if you're not using a repository attached to trac you could at least maintain the repository for tracking changes to your config and make use of the subversionnotify component to tell you things have changed. The point is to use revision control for Trac's configuration (and in Craig's case Postgres and Apache as well). This wouldn't even need to be publicly (or at least to users on your network) if you didn't want... just a local repository on the machine hosting Trac that you work with. Though I think it would probably be better to set it up properly so everyone who needs to access it has an account which would allow you to know who made the change (or at least I'd think this is possible based on the description of subversionnotify on their site) and to make those changes without having to login directly to the machine hosting Trac (either to dump files in a share or make the edits on the machine). Ben On Wed, Feb 8, 2012 at 6:45 AM, dkl13 <[email protected]> wrote: > This is a trac with no matching svn. > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/trac-users/-/iJQ5_SHGRt8J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
