b22e89001a9bd5bd31c320d68b5a1b5bde4aef24
Test and deploy / test-and-deploy (pull_request) Successful in 2m25s
Two jobs meant checking out, setting up Node and running npm ci (and in the frontend the build) twice, about two minutes each, because every job starts in a fresh container. Now one job tests and, for pushes to master only, deploys. The push-to-master condition is spelled out on every deploy step instead of an env flag compared to 'true', which would skip the deploy silently and stay green if the boolean were rendered differently. A failed test still stops the deploy (an if: without a status function implies success()). Docs: the one-job layout, and that Jenkins deployed as root - files it left in an app folder must be chowned to the subscription user before the first Gitea deploy (hit on the API). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nachklang Calendar
Event calendar for Nachklang e.V.: a public landing page for subscribing to the calendar, and an
admin area (/admin) for editing events in all calendars.
Next.js (App Router) + TypeScript + Tailwind + shadcn, the same stack as nachklang-feedback.
Rewritten from Angular in September 2026 (docs/rewrite-plan.md).
Documentation: architecture · features · gotchas · deployment · API wish list
Development
cp .env.local.example .env.local # then adjust if needed
npm install
npm run dev # http://localhost:4200
Port 4200 is not arbitrary: it is the port the API's better-auth origins and the admin app's redirect allow-list trust. Another port breaks sign-out and the return redirect after sign-in.
The admin area needs the API (:3000) and the admin app (:3002) running locally.
Other scripts
npm run build # production build (output: standalone; see docs/deployment.md)
npm run lint
npm test # Vitest, pure logic in lib/
Languages
TypeScript
97.2%
CSS
2.6%
JavaScript
0.2%