Files
parking_solution/wiki/entities/technology-stack.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

1.1 KiB

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

Technology Stack

The standing stack for the parking system. Every choice is MIT/Apache/BSD — a deliberate constraint to avoid vendor lock-in and license rug-pulls (see payload-cms for the cautionary case). (See parking-system-architecture §2.)

Layer Choice License
Monorepo turborepo MIT
Backend fastify (Node.js) MIT
Frontend react-vite-spa MIT
Local database sqlite (better-sqlite3) Public domain / BSD
ORM drizzle-orm (+ Drizzle Kit) Apache 2.0
Remote sync target PostgreSQL (when implemented) PostgreSQL License
Auth local-jwt-auth (@fastify/jwt + bcrypt + roles) MIT

Why these

One language end-to-end (Node), a mature ecosystem for device I/O (serialport, node-hid, escpos), and a database whose only real limit (single-writer) a parking workload never approaches. The stack is shaped by offline-first: nothing depends on a network at runtime.

See standing-decisions for the full list of settled decisions.