I host most of my personal projects on code.liw.fi. It has version control repositories, bug trackers, release files, and Debian apt repositories, and perhaps other data. Home pages for the projects are elsewhere, the code site is only for static files, not wikis etc.

Each project has a sub-directory of its own. Thus, project foo would be at http://code.liw.fi/foo/, with all files specific to it under that directory. Debian packages are an exception: they are all collected into the same repository.

Release tarballs

I do not currently provide release tarballs, except as part of building a Debian package. To find those tarballs, browse http://code.liw.fi/debian/pool/main/.

Bazaar repositories

I put any public branches I publish at

http://code.liw.fi/$PROJECT/bzr/$BRANCH/

I only provide http access to them, since I do not want to run a bzr server on the host. If this ever becomes a problem, I might run the bzr server, or move the branches elsewhere.

Most projects only have a trunk branch.

The branches cannot be browsed with a web browser; you need bzr to access them. I do not want to run loggerhead or such software myself. Again, if this ever becomes a problem, I might change things.

The command to get the code with bzr is:

bzr branch http://code.liw.fi/$PROJECT/bzr/$BRANCH/

The Debian repository

I maintain an apt repository with packages for my personal projects. I use the packages myself, and I often depend on them, so they usually work for me, but I make no guarantees. I only provide packages for amd64 and i386 architectures, and do not guarantee that everything is built for both architectures. I also typically only provide packages for one Debian release, though the packages may well work in other releases.

You're welcome to use the repository. To do so, add the following to your sources.list file:

deb http://code.liw.fi/debian squeeze main

The PGP key that is used to sign the Release files is at

http://code.liw.fi/apt.asc

I have signed the key with my personal key, so you can verify it using the usual Web of Trust mechanisms.

Bug trackers

I use SD for bug tracking. Each project that has a bug tracker has it at

http://code.liw.fi/$PROJECT/bugs/

The bug database can be browsed as static HTML files, but that is a read-only interface. If you want to report a bug on one of my projects, you should e-mail the project-specific mailing list (if one exists), me directly, or add a comment to the project's wiki page.

To use the bug tracker, do this:

mkdir $PROJECT-bugs
SD_REPO=$PROJECT-bugs sd clone --from http://code.liw.fi/$PROJECT/bugs

See the SD documentation for more information. sd help is a good place to start.