Run BisQue locally
Start the supported BisQue development environment and find its local services.
The supported development workflow runs the BisQue API, workers, and frontend from the checkout. PostgreSQL runs in Docker, while the workflow execution slice uses the project’s pinned local Kubernetes environment.
Prerequisites
Section titled “Prerequisites”Install Nix with flakes, Docker, direnv, and Just. Then run these commands from the backend
directory:
direnv allowjust setupjust devOpen the URL printed by just dev. The default local account is:
Username: adminPassword: bisqueThese credentials are for the local development composition only.
Check the environment
Section titled “Check the environment”just dev-statusjust urlsThe API normally listens at http://localhost:8000. Its primary operational endpoints are:
/health/live— process liveness;/health/ready— dependency readiness;/api/docs— interactive API documentation; and/api/v1/openapi.json— the OpenAPI contract.
Enable optional tools
Section titled “Enable optional tools”Options compose with the standard development command:
just dev --authentik --mailpit --observeUse --authentik for the local OpenID Connect provider, --mailpit for email and password-reset
testing, and --observe for local logs and dashboards.
For architecture and dependency boundaries, read the maintainer
architecture guide. The repository’s README.md remains the complete
command reference.