RE: Integrity checking for FSFS repositories.. tripwire, etc.?

My gut reaction is that you should make your publicly-viewable
repository read-only. Basically, have a post-commit hook replicate the
repository from one location to the other. Either that, or a
daily/hourly/15-minutely cron-job to scp/sftp the data over. You get
the open-source data to the world, just not 100% timely.

This of course doesn't solve the problem of other people contributing
code. Maybe make this an out-of-band method (email). Heck, if you're
going the snapshot route, maybe just do a daily checkout, and put a tgz
file up on your public server for consumption.

Just some thoughts..

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 5 17:44:55 2005