Originally Posted by
Graham
I'd suggest providing an rsync server, to make it easy for people to host mirrors and keep them up to date with minimal bandwidth/manual intervention required. I'd possibly be interested in running a mirror if you did this, depending on disk usage requirements.
I've been working on a cache archiving service for new engine clients which stores the data internally in a content-addressable format. It is converted into the standard main_file_cache.dat2/idx format on demand. This has several benefits, one of which is deduplication - the amount of disk space required to archive every single cache we have should be vastly reduced. (Another advantage that naturally drops out of using a content-addressable format is missing files can be found from nearby caches if the checksum/version are identical.) I'm hoping to start running it in production in a few weeks.
I think it'd complement your project quite nicely, as my main interest is in archiving the original data (clients, caches and XTEA keys) and not servers, tools, documentation, etc., which you do seem to be archiving.