From clone to login,
in a few commands.

Make sure the following tools are available before you begin:

A container engine — Podman or Docker with Compose — is recommended for the captcha support service.

Clone the repository and enter the project directory:

The default local configuration expects a database named ticketdb and a user ticketdb with password ticketdb. Create them:

billetsys connects to PostgreSQL on localhost:5432 by default. Override with DB_HOST and DB_PORT if needed. To start fresh, dropdb ticketdb then recreate it.

billetsys uses a local CAP service for captcha protection on the password-reset flow. Start it before the application:

This detects Podman Compose or Docker Compose and starts the containers in docker-compose.yml. If neither is installed, the step is skipped with a warning.

Start the application in Quarkus development mode:

On startup, billetsys connects to PostgreSQL, updates the schema, and loads bootstrap data. In dev mode, outgoing email is mocked so you can test notification flows without a mail server.

The seeded development users let you explore every role immediately:

Additional seeded accounts include user2, userb, superuser2, tam2, and support2. See the Getting Started guide for the full list.