Talk:Subversion managed home directory

I like the idea of using svn and its flatfile system. I can be accessed in multiple ways: apache module, svn:/// and svn+ssh:///. This should make it easy to secure, if you own the server. Also svn reposistories can be setup anywhere on the disk using svnadmin, I believe this would make it easier to keep everything to set it up in userland, not that it is a big deal.


 * Flatfiles as opposed to the database files that svn can use? Personally I'm a little wierded out about the database files as well. I wonder how svn works with binary files.  Any ideas?  Encrypted directories would be realized as file.aes files. RandomTask 22:08, 12 January 2006 (CST)


 * Check page 278 of the svn-book.pdf it talks about binary files. It looks like it is smart enough to determine if it is binary data, and if it gets it wrong you can set it by setting a mime type for it. As for encrypted directories, Do you think it would be better to place both the repository and the local copy in encrypted directories and then update/commit the files within the direcories rather than the "files.aes" that way you get the versioning on the files within rather than the binary encrypted data. Maybe check into the capabilities of the commit scripts to mount the encrypted directory during update and commit? --Langseth 04:08, 14 January 2006 (CST)