WebDAV
Installed an running. Upgraded to run the YourKit profiler. Also, I’m moving servers this month, and I want to unify my services before I move, reducing the servers I run to a bare minium.
Thus, I want to work with WebDAV. Instead of running in integration builds on the server, I’d like to run them locally, on my OS X machine or Linux machine. Then I’d like to publish. Rather configuring a networked Ant build, I like to simply copy the results to a directory, and have that directory magically appear on the server.
This could be done by serving directly out of Subversion, for otherwise static things like test results. Perhaps, through a caching proxy, if Subversion is too slow.
The crux of the idea is that all trasfter is done via HTTP, WebDAV, SMTP, IMAP or SCP. Many protocols to chose from, but only five servers to run; Apache 2.0, Jetty, qmail, CourierIMAP, and sshd.
I’ve mounted one of my Subversion repositories as file share already. There is information that I won’t want to version, and I can use standard WebDAV for that.
Trouble in paradise, already. Spotlight won’t be able to track changes to a WebDAV mounted drive, so indexing needs to be run manually. This is very slow, and chews up a bit of bandwidth. Oh, and it doesn’t work. I’m searching now that the index is built, and I’m getting no results what-so-ever.
Oh, well. That’s okay. I still get drag and drop organization of Subversion repositories, fore those that are holding data and documents, not source code, that is very useful. I can get the spotlight search through a checkout.
So, I can use the command line and SVN X to manage documents when editing, and use WebDAV for auto storage, and drag and drop storage. Before using WebDAV from OS X, go and turn off .DS_Store creation.
References used are Apache 2.0 mod_dav. I’ve had Subversion running as DAV forever, so I have no notes on that. There is a Linux WebDAV filesystem that I am going to install on my older laptop. Then I can use that old laptop to run integrations and publish, taking pressure off the server CPU. Some straight-forward instructions on installation of the filesystem.