Commit Graph
46 Commits
Author SHA1 Message Date
Paddy 8410d9f63a Merge pull request 'Run tests and deploy in one Gitea Actions job' (#24) from feature/ci-single-job into master
Test and deploy / test-and-deploy (push) Successful in 2m37s
Reviewed-on: #24
2026-11-08 21:56:06 +00:00
PaddyandClaude Opus 5.5 b22e89001a Run tests and deploy in one Gitea Actions job
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>
2026-11-08 22:51:26 +01:00
Paddy 689a485fce Merge pull request 'Support the read-only calendar role, show "Vorstand", fix link buttons' (#23) from feature/calendar-readonly into master
Test and deploy / test (push) Successful in 2m25s
Test and deploy / deploy (push) Successful in 2m16s
Reviewed-on: #23
2026-11-08 21:38:39 +00:00
PaddyandClaude Opus 5.5 c142c45edf Note on the API wish list that moving an event leaves no history
Test and deploy / test (pull_request) Successful in 2m16s
Test and deploy / deploy (pull_request) Skipped
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 22:36:11 +01:00
PaddyandClaude Opus 5.5 61e0393f01 Support the read-only calendar role, show "Vorstand", fix link buttons
Test and deploy / test (pull_request) Successful in 2m18s
Test and deploy / deploy (pull_request) Skipped
- Read-only role: /admin/me's permissions decide via canEditCalendar
  (lib/permissions.ts, mirrors the API's canWrite: only `access` writes).
  Read-only accounts see everything but get no "Neuer Termin", no "+", no
  "Veröffentlichen"; an event opens as "Termin ansehen" with locked fields.
  A "Nur lesen" badge in the header explains why. The API refuses their
  writes regardless.
- The management calendar is labelled "Vorstand"; the slug stays
  `management` for the API, URLs and iCal links.
- The subscription dialog's Apple/Google links are plain anchors styled with
  buttonVariants instead of Base UI Buttons rendering an <a>, which warned in
  dev and would have given them role="button".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 22:15:31 +01:00
Paddy 1971d2bd6f Merge pull request 'Rewrite the calendar frontend in Next.js' (#22) from feature/nextjs-rewrite into master
Test and deploy / test (push) Successful in 2m26s
Test and deploy / deploy (push) Successful in 2m18s
Reviewed-on: #22
2026-11-08 20:54:09 +00:00
PaddyandClaude Opus 5.5 38eff139be Document the real deploy setup: SSH port, deploy user, shared key
Test and deploy / test (pull_request) Successful in 2m29s
Test and deploy / deploy (pull_request) Skipped
- SSH on port 42069, deploy user plesk-nachklang, one deploy key for all
  Nachklang repos as a Gitea organisation secret (host, port and user as
  organisation variables; path and build values per repository).
- Key-only login for the deploy user via a Match block in sshd_config.
- Plain /bin/bash instead of Plesk's chrooted shell: bash segfaults in the
  chroot copy on this server, so every session closed right after login;
  the read-access trade-off and a stricter rrsync option are noted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 21:46:54 +01:00
PaddyandClaude Opus 5.5 b0cd657fd9 Deploy with Gitea Actions instead of Jenkins
Tests every push and pull request (lint, typecheck, Vitest, production
build); pushes to master build the standalone bundle in the runner and
rsync it over SSH as the subscription user into the subdomain's Plesk
folder, then restart Passenger via tmp/restart.txt. No mounted host paths;
rsync --delete leaves tmp/ and .well-known/ alone. Optional smoke test once
DEPLOY_SMOKE_URL is set.

Setup (deploy key, pinned host key, Gitea secrets and variables, Plesk
Node.js settings) and the switchover order are in docs/deployment.md.
Checked locally with actionlint and against a throwaway SSH server, which
also caught "~" in the rsync -e string resolving to the wrong home.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 21:09:19 +01:00
PaddyandClaude Opus 5.5 0cda40f85e Rewrite the calendar frontend in Next.js
Replaces the Angular 18 app with Next.js 16 / React 19 / Tailwind 4 / shadcn,
the same stack and design system as nachklang-feedback, planned in
docs/rewrite-plan.md.

- Admin: all calendars in one mobile-friendly list (month groups, calendar
  chips, Kommend/Vergangen/Alle, search, sort, filters in the URL), an edit
  sheet for create/edit/duplicate/delete, publish confirmation, and an
  "Abonnieren" dialog with subscription links for every calendar.
- Public landing page: subscribe links from env instead of hardcoded, plus
  the next public events, server-rendered and revalidated every 5 minutes.
- All times handled explicitly as Europe/Berlin; whole-day events stored as
  00:00-23:59. Fixes carried over from the Angular app: the move dialog
  leaking a cancelled calendar change, saves that looked saved when they
  failed, in-place Date mutation, and duplicated calendar-id mappings.
- Same shared-session auth as before (proxy.ts gate, /admin/me, 401 vs 403).
- 112 Vitest tests over lib/; docs in docs/ (architecture, features,
  gotchas, API wish list, deployment).

Needs the API branch feature/calendar-ical-escaping-subscriptions deployed
first (GET /calendar/events/subscriptions).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-28 22:15:59 +02:00
Paddy f82255961b Sign in through the admin app instead of this one (#20)
Jenkins Production Deployment
Reviewed-on: #20
Co-authored-by: Patrick Müller <mail@pmueller.me>
Co-committed-by: Patrick Müller <mail@pmueller.me>
2026-09-06 21:13:12 +00:00
Paddy ded89d54f3 Merge pull request 'Claude init file + div. improvements' (#19) from feature/aiImprovements20260502 into master
Jenkins Production Deployment
Reviewed-on: #19
2026-06-28 12:01:02 +00:00
Paddy 6400616335 Redesign calendar landing page 2026-06-28 14:00:47 +02:00
Paddy 55748260d0 Claude init file + div. improvements 2026-05-02 14:29:23 +02:00
Paddy 8b0d1ca228 Update admin view to include the new birthdays calendar
Jenkins Production Deployment
2025-09-07 18:39:26 +02:00
Paddy a2ef25ad34 Update admin view to include created date and last modified information
Jenkins Production Deployment
2025-05-29 13:32:20 +02:00
Paddy 2d09046976 Fix issue where not all events would be displayed due to missing scroll functionality if the table contained too many rows.
Jenkins Production Deployment
2024-11-02 19:02:41 +01:00
Paddy dfa00a85ad Forgot to add files of new component *facepalm*
Jenkins Production Deployment
2024-06-04 16:43:52 +02:00
Paddy a0f6d85e1b Add ability to move events between calendars
Jenkins Production Deployment
2024-06-04 16:34:49 +02:00
Paddy 42021b50bc Add new "choir" calendar 2024-06-04 11:22:27 +02:00
Paddy 20691514b9 Add hint for activation email
Jenkins Production Deployment
2023-12-30 23:04:50 +01:00
Paddy 543bb182b9 Styling improvements because Sophia complained :D
Jenkins Production Deployment
2023-08-22 18:29:08 +02:00
Paddy b1f8667705 Fix a bug that would wrongly show a date validation error when creating whole day events
Jenkins Production Deployment
2023-08-05 20:43:44 +02:00
Paddy 469c83856d #15: Improve error handling during login
Jenkins Production Deployment
2023-08-05 18:10:29 +02:00
Paddy ab9c579765 #16: Setting end date automatically if end date is before start
Jenkins Production Deployment
2023-05-16 20:30:23 +02:00
Paddy 0861294534 Add draft as default status for new events
Jenkins Production Deployment
2023-05-15 21:04:09 +02:00
Paddy 0962a36b59 Enable UI to work with event status 2023-05-15 21:00:28 +02:00
Paddy 39ffa5e52c Fix issue on login where user info would not be displayed properly
Jenkins Production Deployment
2023-05-14 21:17:56 +02:00
Paddy 9ed6f9968e Upgrade to proper user management
Jenkins Production Deployment
2023-05-14 21:08:55 +02:00
Paddy c772b01e7d Add subscribe link to landingpage
Jenkins Production Deployment
2022-12-29 14:38:36 +01:00
Paddy 5f9134837a Hide delete button for new events
Jenkins Production Deployment
2022-12-28 16:46:31 +01:00
Paddy 418b5fc4a0 Tidy up code
Jenkins Production Deployment
2022-12-28 16:32:26 +01:00
Paddy a1c46c2648 #8: Add URL check
Jenkins Production Deployment
2022-12-28 16:25:23 +01:00
Paddy 754408dfa3 More performant implementation of event filter
Jenkins Production Deployment
2022-12-28 15:27:31 +01:00
Paddy bafc56d604 #11: Reload button
Jenkins Production Deployment
2022-12-28 15:04:58 +01:00
Paddy 8fa2b8cb5f Add sorting options
Jenkins Production Deployment
2022-12-28 15:00:56 +01:00
Paddy 1990c9a42d #7: Adding filters
Jenkins Production Deployment
2022-12-28 14:10:39 +01:00
Paddy 85ffaea589 Improve deletion warning
Jenkins Production Deployment
2022-12-28 12:39:14 +01:00
Paddy aa0d03c86a #6: Add ability to create whole-day events
Jenkins Production Deployment
2022-12-28 12:33:20 +01:00
Paddy effb0efb6d Fix login page labels
Jenkins Production Deployment
2022-12-27 13:55:44 +01:00
Paddy 2628313007 Add delete capabilities
Jenkins Production Deployment
2022-12-27 13:49:16 +01:00
Paddy 8ae121ca0c Finish edit capabilities and add adding capabilities 2022-12-26 15:59:24 +01:00
Paddy 6dd89e4c69 Bump deps 2022-12-26 13:51:54 +01:00
Paddy 48781b33fe remove vsc folder 2022-12-25 21:25:28 +01:00
Paddy c80312de9d Add first version of admin table with basic edit capabilities 2022-12-25 21:24:17 +01:00
Paddy 6822bb8a04 Add components 2022-12-25 17:48:24 +01:00
Paddy 67ec11d90d initial commit 2022-12-25 16:30:56 +01:00