Code Club Cambridge

Project resources for Code Club Cambridge, built as a React application with a small Express server.

Toolchain

• Node.js 24 LTS
• Yarn 4 workspaces
• React 19 and React Router 7
• Mantine 9
• Vite 8 and Vitest 4
• TypeScript 6, ESLint 10, and Prettier 3

Development

Install dependencies and run the UI and API together:

corepack enable
yarn install --immutable
yarn dev

The UI runs at http://localhost:5173 and proxies /api requests to the Express server on port 3001.

Quality checks

yarn validate

This checks formatting and lint rules, type-checks both workspaces, runs the browser-facing regression tests, and creates the production build.

Production

yarn build
yarn start

The Vite build is written to ui/build, which the Express server serves along with its API routes.

Mentor tools

Approved mentors sign in with Google at /manage/schedule to publish calendar changes, or at /manage/projects to add a learning project. Access is checked against a case-insensitive email allowlist on every write.

Create a Google OAuth client with the Web application type and register these redirect URIs:

• http://localhost:5173/auth/google/callback for local development
• https://code-club-host.exe.xyz/auth/google/callback for production

The application requests only the OpenID, email, and profile scopes. Configure it with:

PUBLIC_URL='http://localhost:5173' \
GOOGLE_CLIENT_ID='your-client-id' \
GOOGLE_CLIENT_SECRET='your-client-secret' \
AUTH_ALLOWED_EMAILS='mentor-one@example.com,mentor-two@example.com' \
SESSION_SECRET='at-least-32-random-characters' \
yarn dev

Generate a strong session secret with node -e "process.stdout.write(require('crypto').randomBytes(32).toString('hex'))". In production, add GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, AUTH_ALLOWED_EMAILS, and SESSION_SECRET as secrets in the GitHub production environment. The deployment fails rather than publishing an editor with incomplete authentication.

Content database

Schedules and projects are stored in data/codeclub.sqlite locally and in the existing schedule-data Docker volume in production. On first startup, the database imports the existing project catalogue and any previously published data/schedule.json, so enabling OAuth does not discard calendar changes. New mentor projects are published to the main project catalogue immediately.

Deployment

The production mirror runs in Docker on the code-club-host exe.dev VM. A successful Validate workflow for a push to master triggers .github/workflows/deploy-exe-dev.yml, which uploads that exact commit and waits for the container health check before verifying the public endpoint.

The GitHub production environment requires an EXE_DEV_DEPLOY_KEY secret. Register its public key in exe.dev with the codeclub-deploy tag, and give the production VM the same tag so the key cannot access unrelated VMs:

ssh exe.dev ssh-key add --tag=codeclub-deploy 'ssh-ed25519 AAAA... github-actions-codeclub-deploy'
ssh exe.dev tag code-club-host codeclub-deploy

The VM must be public and proxy port 8000:

ssh exe.dev share port code-club-host 8000
ssh exe.dev share set-public code-club-host

For a manual deployment from an uploaded checkout:

DEPLOY_SHA="$(git rev-parse HEAD)" ./ops/deploy.sh