jacobh2
02db5430eb
Security - Every route now requires a login and refuses ids outside the caller's workspace with 404: plan, leave-wishes, day-overrides and vacation-days were fully anonymous; every other router trusted client-supplied workspace/child/parent ids. Scraper sessions are bound to their owner. - Invitations can no longer be created for a foreign workspace, and a redeemer who is already a member (or a full workspace) is refused. - Production refuses the default JWT secret; API docs are hidden in production; a failed migration aborts startup instead of serving. - Login and register no longer reveal whether an email exists; inactive accounts are rejected; /auth/refresh is rate limited. - The FK scraper writes debug artefacts only when explicitly enabled, logs no scraped values or page text, clears the BankID QR as soon as it is scanned and purges finished sessions after five minutes. - Real FK page captures are removed from the tree (history rewrite follows); the parser tests use a synthetic fixture. Performance and correctness - Plan apply/sync run inside one locked transaction with batched writes instead of one commit per row, so a failure mid-batch leaves nothing half-applied and concurrent syncs no longer corrupt each other. - SQLite runs in WAL mode with a busy timeout; 14 indexes cover the filters that were full scans; argon2 hashing runs off the event loop; responses are gzipped. - Frontend: a 401 now refreshes the token once and retries, so sessions no longer die silently after 15 minutes; every data hook discards stale responses; logout clears state even when the server call fails. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CsXCCcDfmV4Sps4ZQSvNEY
69 lines
2.8 KiB
Markdown
69 lines
2.8 KiB
Markdown
# Backend — Föräldraledigplannerare
|
|
|
|
FastAPI + Python 3.14, packages managed with `uv`. Layered architecture
|
|
(entities → repositories → services → routers) with dependency injection so the
|
|
database backend (SQLite now, Postgres later) is swappable.
|
|
|
|
## Setup
|
|
|
|
```bash
|
|
uv sync # install deps (incl. dev group)
|
|
uv run uvicorn app.main:app --reload # run dev server on :8000
|
|
uv run pytest # run tests with coverage
|
|
uv run ruff check . # lint
|
|
```
|
|
|
|
## Configuration
|
|
|
|
Key env vars (prefix `APP_`, see `.env.example`):
|
|
|
|
- `APP_ENV` — `development` (default) | `test` | `production`. In production,
|
|
`Settings` refuses to start unless `APP_JWT_SECRET` is a random value of at
|
|
least 32 characters (the shipped dev default is rejected). Production also
|
|
disables `/docs`, `/redoc`, and `/openapi.json`.
|
|
- `APP_JWT_SECRET` — required to be a strong, random secret in production.
|
|
- `APP_LOG_LEVEL` — default `INFO`.
|
|
|
|
## Layout
|
|
|
|
```
|
|
app/
|
|
config.py # pydantic-settings (app config + frozen LeaveRules)
|
|
dependencies.py # DI factories (pick repo impl by settings.database_type)
|
|
entities/ # plain dataclasses (domain)
|
|
models/ # pydantic API schemas
|
|
repositories/ # abstract interfaces
|
|
repositories_impl/ # concrete impls per backend (sqlite/, postgres/)
|
|
services/ # business logic
|
|
routers/ # FastAPI routes
|
|
db/connection.py # connection + (dev) schema bootstrap
|
|
utils/ # errors, logger
|
|
```
|
|
|
|
## Demo data (manual/browser testing)
|
|
|
|
`scripts/seed_demo.py` seeds a realistic, ready-to-explore workspace through the
|
|
normal service/repository layers (no raw SQL) — a couple workspace with a
|
|
partner, a child born ~6 months ago, vacation rows for only some years (so the
|
|
`is_assumed` badge is visible), day overrides, and a spread of leave wishes
|
|
(fixed, flexible, and one deliberately underfunded to show a shortfall +
|
|
remedies + surplus advice). Login credentials are fixed and printed at the end.
|
|
|
|
```bash
|
|
uv run python scripts/seed_demo.py # create once; re-running is a no-op
|
|
uv run python scripts/seed_demo.py --reset # wipe the demo workspace and rebuild
|
|
```
|
|
|
|
Then open `http://localhost:5173` and log in with the printed `demo@example.com`
|
|
credentials. Safe to re-run: without `--reset` it detects the existing demo
|
|
user and changes nothing; `--reset` only ever deletes the one demo workspace.
|
|
|
|
## Reference vertical slice
|
|
|
|
`VacationDays` is implemented end-to-end (entity → schema → repo interface →
|
|
SQLite impl → service → router → tests). **Copy this slice** when adding a new
|
|
entity.
|
|
|
|
> The inline schema in `db/connection.py` exists only so dev/tests are
|
|
> self-contained. Production schema is owned by Alembic migrations (a senior task).
|