Skip to content

Website v1.0.7

For everyone: what changed in this release of the website. Released 2026-10-24.

Highlights

The contact and course registration forms now answer at once. The emails they send (the notice to staff and the confirmation to you) are queued and follow within minutes, so a problem with our mail service no longer shows you an error or loses your message.

Features

  • Sending a form no longer waits for the emails. You see the success message straight away, and the emails arrive shortly after.
  • If our mail service is down or slow, your submission is still saved and the emails are sent as soon as it is back. Nothing needs to be sent again.
  • If a notice to staff can never be delivered, we are alerted and follow up by hand.

Fixes

  • A mail outage no longer makes a form show "Something went wrong" after your details were already saved.

Operations

  • One migration, 0003: an email_outbox table that holds the emails until they are sent. Forms no longer send mail themselves.
  • New required secret JOBS_TOKEN (at least 32 characters) in each environment's enc.app.<env>.yaml. The app refuses to start without it. See Configuration and Rotating secrets.
  • Two timers on the server call the app: the email sweep every 2 minutes and a daily cleanup at 21:45 UTC (03:15 Sri Lanka). They have four healthchecks.io checks, website-{prod,dev}-{outbox,cleanup}, so the monitoring now has sixteen checks. See Scheduled jobs.
  • The cleanup removes the content of sent and failed emails after 30 days, the rows themselves after a year, and old form-limit counts. If a staff email has failed for good, the cleanup answers with an error so its check goes down until the operator acts. See Website email outbox.

Upgrade notes

  • Before the first deploy of each environment, the operator adds JOBS_TOKEN to its enc.app.<env>.yaml (sops, openssl rand -hex 32). Without it the app refuses to start and the deploy goes red.
  • The timers come after the release: create the four healthchecks.io checks, add them to enc.server.yaml, and run just provision in the managed leaf (infra_managed_vps_hostinger) once the version is live. Provisioning earlier would make the timers call v1.0.6, which has no jobs route.
  • Emails that were already sent are not affected. Rows in the outbox appear only for submissions made on v1.0.7.
  • Rolling back to v1.0.6 needs no database step, but emails still waiting in the outbox are not sent by the older version, and the timers answer 404 (their checks alert) until the site is rolled forward again. See Deploy and rollback.
  • Developers with EMAIL_BYPASS=true locally now need JOBS_TOKEN in .env.local too (openssl rand -hex 32).