Les Mikesell wrote:
>
> As someone who deals with about 10 gigs (compressed) of web logs a
> month,
> I have to wonder why anyone would want to put timestamped lines that
> never
> change into a revision control repository that won't allow you to
> ever delete anything. 'rsync -essh' works if you just need a transport.
>
Our logs only grow about 1GB per month (uncompressed). If/when the
repository gets too big and I decide that I don't want to keep log files
from 2000 any longer, we'll simply do a dump/restore to a new repository
every few years. Or the same repository.
I think one advantage over rsync might be that the web server can't
delete older log files. Due to the locked down nature of the SSH key
along with a heavily locked down SSHD configuration, the web server
machine shouldn't be able to do damage. The worst it can probably do is
an "svn del" against the repository, which can easily be undone. I
might also implement an IP address filter on the SSH key.
It's useful for us because we already have an SSH key structure in
place, SVN is installed, and if a developer / admin wants to look at log
files, they're as easy to get to as any other repository. So there's
little training or hand-holding needed.
But mostly it was done as a test exercise to see how well it worked.
Necessary? Maybe not. But it sharpened my SVN admin skills.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 20 23:50:46 2006