4
1
I've been bitten by the SVN bug lately; largely driven by heavy use of a personal repo at work for keeping control of proof-of-concept code, documents and small files, and for keeping my two machines in sync.
My home NAS, a D-Link DNS-323, is a solid little box with some extra scripts and packages installed to provide some daily backups--but it also has a few shortcomings that keep it from being used like I'd like to. My hopes were to use it as my always-on fileserver for home and remote use--but the permission controls are fairly weak and inflexible and access to it from outside my home network is limited to SSH/SCP and FTP (which is only turned on temporarily if ever).
So I thought to myself: what if I used it primarily as an SVN-based fileserver and allowed remote access via SSH+SVN. I could still have a non-SVN windows share for large files such as my laptop backups; but I could by-and-large use it as an SVN-repo for personal files.
The question here is where do I stop, what are the limitations on SVN regarding maximum repo size or size of files stored in it?
Oh, just remembered another one: when doing a checkout of my home directory to a brand new machine, I have to make sure I touch the mbox index files so that kmail doesn't rebuild them and throw out the read/replied/etc flags on it. Using maildir instead of mbox runs into the 3rd drawback that I already mentioned. – retracile – 2009-08-13T16:34:33.173
Retracile, you can edit your answer to include your comment. On a related note, you can also delete your comment after incorporating it into the answer. – Travis – 2009-08-19T18:47:04.710