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
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.
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/.
I put any public branches I publish at
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 currently support squeeze, wheezy, and unstable: I plan to support the current Debian stable and unstable, adding testing when it's frozen, and remove oldstable after I no longer need it myself.
You're welcome to use the repository. To do so, add the following
deb http://code.liw.fi/debian squeeze main
I have signed the key with my personal key, so you can verify it using the usual Web of Trust mechanisms.
I use this wiki for bug tracking. Each project has a link to its bug list. Most of the time I prefer you to report the issue or bug by e-mail, and I'll add it to the wiki myself.