- Docker passes ENABLE_BANKING_APP_ID and ENABLE_BANKING_PRIVATE_KEY through - transactions are keyed on entry_reference: Enable Banking says transaction_id may change between fetches, which imported rows twice - a key pasted on one line keeps its own PEM label (PKCS#1 keys broke before) - nginx keeps X-Forwarded-Proto/Host from a reverse proxy, so return links are https - README: how to set up the app, the keys, and https if Enable Banking needs it Checked against Enable Banking's API docs and tested end to end against a stand-in. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brokeless in Docker
Everything runs here: the app, its Postgres database, sign-in and the REST API (the parts of Supabase it uses), a mail catcher for sign-in links, and optionally Ollama for AI. No Supabase cloud, no Vercel, no auto-update.
| Container | What it does | Port |
|---|---|---|
| gateway | nginx: broke plus /auth/v1 and /rest/v1 on one address |
HTTP_PORT (3003) |
| broke | the app, built from this checkout | inside only |
| db | Supabase's Postgres image | inside only |
| auth | Supabase Auth (GoTrue): email sign-in links | inside only |
| rest | PostgREST: the database API, row-level security applies | inside only |
| mailpit | catches sign-in emails, behind a password | MAIL_UI_PORT (8025) |
| ollama | local AI, only with --profile ai |
inside only |
First start
-
Pick the address you will open broke on, for example
http://192.168.1.10:3003(your Unraid IP; notlocalhost, the containers need to reach it too). Then make the secrets:node docker/setup.mjs --url http://192.168.1.10:3003No Node on the server:
docker run --rm -v "$PWD":/w -w /w node:22-alpine node docker/setup.mjs --url http://192.168.1.10:3003On Unraid, edit
docker/.envand setDATA_DIR=/mnt/user/appdata/brokeless. -
Start it:
docker compose -f docker/docker-compose.yml up -d --buildWith local AI as well: add
--profile ai, then pull a model, for exampledocker exec brokeless-ollama-1 ollama pull qwen3:8b. -
Open your address, type your email, then open Mailpit on port 8025 (user
broke, passwordMAIL_PASSWORDindocker/.env) and click the link. -
Lock it to you: set
DISABLE_SIGNUP=trueindocker/.env, then runup -dagain. -
Add your bank: Accounts, Add accounts, import a statement. For ING, download your transactions from Mijn ING as CSV (comma or semicolon both work).
Unraid
Install the Compose Manager plugin, add a stack, and point it at this folder's docker-compose.yml, or run the commands above over SSH from the repo folder. Keep the port on your LAN or behind Tailscale. Don't forward it on your router.
Good to know
PUBLIC_URLis built into the app. If your server's address changes, update.envand runup -d --build.- broke's server reaches Supabase through
PUBLIC_URLas well, so the server must be able to reach its own address (it can on Unraid). - Back up
DATA_DIR/dbanddocker/.envtogether. The database is useless without the secrets in.env. - Database changes in
supabase/migrationsapply each time broke starts.
Updating
Nothing updates by itself. See Update in the main README for pulling your own changes and reviewing upstream ones.
docker/db/*.sql come from Supabase's self-hosting setup (Apache-2.0).