therning.org/ magnus

I couldn’t find any information on how to set up darcsweb on lighttpd in general. I was a little disappointed to see that the darcsweb package on Debian only comes with apache and apache2 configurations, nothing for lighttpd. Since Debian is a little special sometimes when it comes to web servers—they like to add convenient configuration “frameworks”—I was afraid that using a “non-supported web server” might be a lot of work. How wrong I was

First enable the CGI module for lighttpd:

# cd /etc/lightttpd/conf-enabled
# ln -s ../conf-evailable/10-cgi.conf

Then create a very short configuration file to enable darcsweb to find its images:

# cd 
# echo 'alias.url += ( "/darcsweb/" => "/usr/share/darcsweb/" )' > \
/etc/lighttpd/conf-available/50-darcsweb.conf

Then enable that “module” as well:

# cd /etc/lightttpd/conf-enabled
# ln -s ../conf-evailable/50-darcsweb.conf

Create your darcs repositories in /var/www/darcs/. I created a repo I called test.

The Debian default configuration of darcsweb will expose all repositories in /var/www/darcs/. This is quite probably not what I wanted so I commented out the auto class and added the following:

class test:
    reponame = 'test'
    repodesc = 'Silly little test repo'
    repodir = '/var/www/darcs/test'
    repourl = 'http://denobula/darcs/test/'
    repoencoding = 'latin1'

That’s it!

I’ve switched from bzr to darcs for all my version management needs. I’ve decided to also move my already existing projects to darcs. First out is epilicious. From now on the following should be used to get the release and development branches respectively:

% darcs get http://therning.org/magnus_darcs/epilicious
% darcs get http://therning.org/magnus_darcs/epilicious.dev

I decided not to take any history with me, I could have used tailor but decided not to, after all this is a very small project. Also, I’m keeping the old history for the time being, it’s in the old place:

% bzr get http://www.therning.org/magnus_bzr/epilicious/
% bzr get http://www.therning.org/magnus_bzr/epilicious.dev/

A while ago I found out that darcs doesn’t work over sshfs out of the box. Of course there was a workaround. Yesterday I was at it again, and this time it was sshfs that gave me grief. After another echange of emails I found a solution.

At the moment this is what’s necessary:

% sshfs -oworkaround=rename <remote path> <local path>
% export DARCS_SLOPPY_LOCKS=1
% darcs put <local path>/<repo name>