Informationen über das Projekt finden Sie in der Dokumentation
Run this whenever you come back to the repo (e.g. on the notebook) after pulling. Every step is idempotent — when in doubt, run all of it.
- Node 24 —
node -vshould printv24.x(the CI version). - Dependencies —
npm install(versions are pinned viapackage-lock.jsonand.npmrc). Supply-chain-guarded variant:npm run how-to-install-using-sfw. - backend-dev secrets —
backend-dev/.envis gitignored. If it is missing, copybackend-dev/.env.exampleand fill in the values; if it is old, diff it against the example.JWT_SECRETmust be ≥ 32 chars and identical for db and PostgREST (both read it from this file). - Backend up —
cd backend-dev && docker compose up -d --build(dev port block 5433/8093, coexists with other local stacks like apf2/ps). On a fresh volume, the first restore ofae.backuptakes a minute — wait untildocker psshowsae_dbas(healthy). - DB migrations — backend/db/migrations/ is applied manually, and every production backup predates at least the newest migrations. They are idempotent, so re-apply all of them:
for f in backend/db/migrations/*.sql; do docker exec -i ae_db psql -U postgres -d ae -v ON_ERROR_STOP=1 < "$f" || break done
- Frontend —
npm run dev→ http://localhost:5174 (it targets PostgREST on localhost:8093 by itself). - Sanity check — log in at
/Loginwithtest-org-admin/ae3-test-pass(seeded bybackend-dev/db/init/05_test_users.sqlon the fresh volume; safe to re-apply on an existing one).
Optional, when the local data should match production again: npm run fetchBackup (writes backend-dev/db/ae.backup), then cd backend-dev && docker compose down -v && docker compose up -d --build — this deletes local dev data — then wait for healthy (step 4) and re-apply the migrations (step 5).