Local development

Getting started

Run RustyAuth and its private SableDB persistence layer locally in a few minutes.

Prerequisites

Docker with Compose v2
Git
A browser with WebAuthn support

Start the stack

git clone https://github.com/rusty-auth/rustyauth.git
cd rustyauth
cp .env.example .env
docker compose up --build

Private by design

The Compose topology publishes RustyAuth only on loopback. SableDB remains on the internal container network and writes to a persistent volume.

Verify readiness

curl --fail http://127.0.0.1:8081/healthz
curl --fail http://127.0.0.1:8081/readyz
curl --fail http://127.0.0.1:8081/.well-known/passkey-auth

The health endpoint proves the process is alive. Readiness confirms the private SableDB dependency is reachable, while capability discovery reports the runtime's backup status.

Check the operator experience

docker compose exec auth passkey-auth-service --help
docker compose exec auth passkey-auth-service doctor

doctor validates configuration, SableDB connectivity, signing-key state and backup access when backups are enabled. The blank backup variables in .env.example deliberately leave the local scheduler disabled.

Next steps

Review WEBAUTHN_RP_ORIGIN, token and backup settings, follow the endpoint contracts in the API guide, and rehearse the backup and recovery workflow.