Modernize BookIT UI, runtime, and deployment

[Portals]

Important

Deployment changes: bookit-node-frontend and bookit-node-backend have been merged into bookit-node.

• Replace both application containers with one using ghcr.io/cthit/bookit:<tag>. Route / and /api/* to its port 8080 and remove the separate frontend deployment.
• Set DB_HOST, DB_NAME, DB_USER, and DB_PASS; DB_PORT defaults to 5432.
• Move the backend environment settings to the combined container and set NODE_ENV=production. Keep the existing SECRET; no new key is required. SESSION_SECRET is accepted only as a compatibility fallback.
• Keep existing PostgreSQL/Redis data volumes. The Alpine container now runs prisma migrate deploy before starting and exits on migration failure. Existing databases previously managed with prisma db push need a one-time baseline after verifying their schema; see the setup and upgrade instructions.
• Local environment examples now live at the repository root. docker compose -f docker-compose.test.yml up --build -d --wait starts the complete local stack and provisions Gamma credentials automatically. docker-compose.prod.yml provides the app, PostgreSQL, and Redis for production.
• Remove the old db-scripts cleanup container or scheduled job. The backend cleans up old booking contact data automatically at startup and daily.
• Existing sessions will require users to sign in again.

Modernizes BookIT across the UI, runtime, and deployment. Replaces the legacy frontend with TypeScript and shadcn/ui, generates GraphQL contracts, strengthens booking concurrency and contact-data privacy, and serves the frontend and API from one container.

Review guide

• Backend: authentication/session handling, booking permissions, transactional overlap checks, and automatic contact-data cleanup.
• Deployment: the migration instructions above, Dockerfile, DB configuration, and the CI → tested image → release flow.
• Frontend: calendar navigation, booking creation/editing/drag confirmation, rules management, and keyboard/mobile behavior.

Dependency changes

Dependency / tooling	Change
Node / package manager	Node 24.19.0; npm replaced with pnpm 12.3.4 workspaces
React / React DOM	17 → 19.2.8
TypeScript	4.9 → 7.0.2
Create React App / ESLint / Mocha / Chai	Replaced with Vite+ 0.3.0: Vite 8.2.2, Vitest 4.1.11, Oxlint and Oxfmt
Digit Components / Material UI icons	Replaced with shadcn/ui, Radix UI 1.6.7, Tailwind CSS 4.3.3 and Lucide 1.41.0
React Router 5	Replaced with TanStack Router 1.170.32; added TanStack Query 5.102.8
FullCalendar	5.9 → 7.1.0, using the Monarch shadcn integration
Moment	Replaced with date-fns 4.4.0
Express	4 → 5.2.1
express-graphql	Replaced with Apollo Server 5.5.1 and its Express 5 integration 1.1.2
GraphQL	15 → 16.14.2; added GraphQL Codegen
Prisma	5.9 prerelease → 7.10.0, with the PostgreSQL driver adapter
Redis client	3 → 6.2.1
express-openid-connect	2 → 3.4.0
Axios / dotenv	0.21 → 1.20.0 / 16 → 17.4.2
ts-node / ts-node-dev	Replaced with tsx 4.23.13
Browser tooling	Added Playwright 1.63.0 and Testcontainers 12.1.0

Removed unused legacy dependencies including express-session, connect-redis, js-base64, qs, prop-types and web-vitals. Moved personal-data cleanup from the separate Jobber container into the backend. Updated CI and container builds for the workspace layout.

Existing PostgreSQL 12 and Redis 5 deployments remain supported. The optional production Compose stack uses PostgreSQL 16; migrating existing PostgreSQL 12 data to it requires dump/restore, not reusing the old data directory.

Issues resolved

• Resolves Be able to change booking date and time by typing #19 — Date and time fields support typing and keyboard navigation.
• Resolves It looks weird when multiple rules are active the same time #70 — Overlapping room restrictions use compact combined labels with full details available.
• Resolves Adding a booking sometimes takes a long time #86 — Booking submissions show a pending state and disable repeat submission; transactional overlap checks prevent duplicate reservations.
• Resolves Remove react-digit-components dependency #110 — Removes react-digit-components and replaces the UI with locally owned shadcn/ui components.
• Resolves Remove drag and drop bookings. #113 — Requires confirmation before saving a dragged booking, as proposed in the issue discussion.
• Resolves Local build failing #116 — Repairs local setup and documents the working development and container workflows.

Screenshots

Desktop

Rules table

Calendar — list view

Calendar — month view

Calendar — week view

Mobile

Mobile — booking form

Mobile — rules table

Mobile — list view

Mobile — month view

[goosetaf]

The desktop week view has strange edges. Also, maybe the label background could be improved somewhat?

[Portals]

The desktop week view has strange edges. Also, maybe the label background could be improved somewhat?

I think I fixed it. Updated the screenshots. @GAsplund

[goosetaf]

The labels, yes I guess. For the edges, not really. Check the top edge for example, where is misaligns:

[Portals]

@GAsplund I see! Check it out, all fixed.

[goosetaf]

The desktop week view has strange edges. Also, maybe the label background could be improved somewhat?

Thanks for the change. However, from my own preference maybe the background dim should be just with a container around the text and not the entire container?

[Portals]

Thanks for the change. However, from my own preference maybe the background dim should be just with a container around the text and not the entire container?

Fixed @goosetaf

[goosetaf]

Having tried to set it up locally, I found a few things:

• Is it possible to use alpine instead of bookworm-slim in the Dockerfile? This would greatly reduce image size
• Having tried to set up my own test compose, I could not get it to migrate. The Dockerfile should probably run database migrations before starting the server
• It would be nice to have a ready-to-go compose file both for production (app + db) and for testing the full environment (that has an additional service that builds and runs the Dockerfile) rather than just a development compose. This would resolve headaches for finding Gamma's test API keys and client.
• It's a bit confusing with the .env.example file being in the bookit directory rather than the root, but I understand if it needs to be there.

[goosetaf]

Nice! I have two more suggestions for the UI, and then I think I'm confident to approve. I have looked through the frontend and backend and I cannot find anything that I have any protest about.

The new color scheme looks a bit dark. Maybe this is a side-effect from attempting to darken the background before?

What exactly is secure here? If it has no real meaning, maybe it should be removed to reduce potential visual clutter.

Edit: third thing. The background is inconsistent depending on if one or multiple rooms are booked. Could also remove the little dot as it does not seem to represent anything in multi-room context.