Contributions are welcome!

The repository is hosted at

Development environment

You can either run the demo locally or with docker. After having launched the demo you have access to several services:

The canaille server has some default users:

  • A regular user which login and password are user;

  • A moderator user which login and password are moderator;

  • An admin user which admin and password are admin;

  • A new user which login is james. This user has no password yet, and his first attempt to log-in would result in sending a password initialization email (if a smtp server is configurated).

Docker environment

If you want to develop with docker, use:

cd demo && docker-compose up

Local environment

If you want to develop locally, use:



On Debian or Ubuntu systems, the OpenLDAP slapd binary usage might be restricted by apparmor, and thus makes the tests and the demo fail. This can be mitigated by removing apparmor restrictions on slapd.

sudo apt install --yes apparmor-utils
sudo aa-complain /usr/sbin/slapd

Populate the database

You can populate the database with randomly generated users and groups with the populate command:

env CONFIG=conf/canaille.toml poetry run canaille populate

Unit tests

To run the tests, you just need to run tox. Everything must be green before patches get merged.

The test coverage is 100%, patches won’t be accepted if not entirely covered. You can check the test coverage with tox -e coverage.

Code style

We use black along with other tools to format our code. Please run tox -e style on your patches before submiting them. In order to perform a style check and correction at each commit you can use our pre-commit configuration with pre-commit install.


The interface is built upon the Fomantic UI CSS framework. The dynamical parts of the interface use htmx.

  • Using Javascript in the interface is tolerated, but the whole website MUST be accessible for browsers without Javascript support.

  • Because of Fomantic UI we have a dependency to jQuery, however new contributions should not depend on jQuery at all. See the related issue.


Translations are done with Weblate, so all translation contributions should be done there.


The documentation is generated when the tests run:

tox -e doc

The generated documentation is located at ./build/sphinx/html.