On Wed, Sep 17, 2008 at 1:55 PM, Jon Schewe <jpschewe at mtu.net> wrote: > I've got a number of servers that have similar configs. The configs that > I make manually I'm keeping in subversion so that we can track changes. > Right now I'm pushing them out to the servers using rsync. The problem > that I've run into is that if someone is debugging a problem on the > server they make changes to the server and if they forget to push the > changes back into subversion the next time the sync script pushes the > files out the changes get overwritten. I would rather be notified on the > next sync that something on the server has been changed since the last sync. > > Has anyone done something like this and have a good solution? I've > thought about unison, and that would probably work, the downside is that > it always needs to be run from the same machine otherwise it doesn't > know the state of the last sync and there are two admins that both may > sync from their workstations. > > Thanks. > Use post-commit hooks in your svn repository to push the changes to the servers. That way, changes will propagate only if they are committed in the repo. Cheers Sunny -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap.