This is the documentation on the deployment of Debexpo.


Here are the basic facts:

Shell account(s)

If you want to make changes to the live site, please first change the dev site and make sure the changes work. That way, we can avoid disrupting service.

In the future, we could do something where changes go into dev and automatically migrate to live after 10 days of no terrible bug reports.

If you have access to the expo account, I think that will be all you need to maintain the service. If you need sudo for something, do ping me (paulproteus).

configuration .ini files

The live ... um I'll finish this in a sec


We use Postgres as the database for storing debexpo data. You c


We use virtualenvs, which are a way to install Python packages without root and with isolation. The dev and live code directories have corresponding virtualenvs. You can access them with:

Your shell's $PS1 will change to indicate which virtualenv is active.

These are shell snippets provided by virtualenvwrapper.

Getting access

If you want access to deploy code, the process is pretty simple:

Right now, the following people have shell access:

We also hang out on #debexpo on

Automatic test suite running through Jenkins

Every few minutes, an automated builder checks for updates in git. If there are any updates, it runs the test suite.

You can see that at