Files
parking_solution/wiki/entities/fastify.md
julian bfe64032d8 Initial scaffold: Turborepo monorepo + design wiki
Turborepo (pnpm workspaces) with all dependencies pinned to latest
mutually-compatible versions: turbo 2.9, TypeScript 6, Fastify 5,
React 19, Vite 8, better-sqlite3 12 + Drizzle ORM 0.45.

Layout:
- apps/server   Fastify backend (local JWT auth + role guard, /health)
- apps/web      React 19 + Vite 8 operator SPA
- packages/db   Drizzle schema on SQLite/WAL; append-only events + users
- packages/devices  reader/printer/relay adapter interfaces (intent-only relay)
- packages/shared   shared domain types

Architecture constraints from the design wiki are encoded in the scaffold:
append-only hash-chained + signed event log, device-agnostic adapters,
"a barrier is not a door" (relay expresses intent only), fully-local
offline-first auth.

wiki/ is an LLM-maintained Obsidian knowledge base (28 pages) ingested
from the architecture & design notes, with its own maintenance schema.

Verified: pnpm install, full turbo build (5/5), server boots and serves
/health, drizzle-kit generates the initial migration.
2026-06-14 00:34:11 +02:00

652 B

type, tags, sources, updated
type tags sources updated
entity
parking
stack
backend
parking-system-architecture
2026-06-14

Fastify

The backend framework (Node.js). Chosen over Express: lighter, faster, with a clean plugin/hook model. (See parking-system-architecture §2.)

  • Hardware drivers live as isolated Fastify plugins emitting onto a shared internal event bus — this is the implementation vehicle for the device-adapter-pattern.
  • Also serves the react-vite-spa frontend.
  • Hosts local-jwt-auth via @fastify/jwt; authorization is a simple preHandler role guard per route.

Part of the technology-stack. License: MIT.