joshua/events-hub
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
chore/deploy-script
events-hub/CHANGELOG.md
T
joshuaandClaude Opus 5.5 5a90c713d8 Deploy script with rollback (1.1.2) 
scripts/deploy.sh backs up the database (pg_dump), checks out the release,
runs npm ci, prisma migrate deploy and generate, builds the frontend,
restarts the PM2 apps and health-checks them. Any failure puts back the
previous code and build, and restores the dump if new migrations had run.
deployment.md §12 now uses it. tsconfig.tsbuildinfo leaves git so builds
don't leave the tree dirty.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 23:55:46 +02:00

3.2 KiB
Raw Permalink Blame History

Changelog

All notable changes to the Cross Events Hub. Format: Keep a Changelog; versions follow Semantic Versioning.

[Unreleased]

[1.1.2] - 2026-10-27

Added

  • scripts/deploy.sh to update the Hub on the server: backs up the database, checks out the release, installs, migrates, builds, restarts PM2 and checks both apps answer. If any step fails it goes back to the previous version, restoring the database if new migrations had run. See deployment.md §12.

Changed

  • frontend/tsconfig.tsbuildinfo is no longer kept in git (builds change it).

[1.1.1] - 2026-10-27

Fixed

  • The install page's Usage card now shows Campuses (Off, or On with the number of active campuses). The Hub already stored campuses and campusCount from the heartbeat but didn't show them; campusCount comes from Cross Events 1.43.0+.

[1.1.0] - 2026-10-27

Added

  • Update requests (docs/hub-protocol.md §3a): POST /api/installs/update-request, signed like the heartbeat. When a church's site admin presses "Request update", the Hub opens an update_requested alert on the install (shown under Alerts and in its history) and emails the alert address once; asking again while it's open doesn't email again. The alert resolves itself when the install's heartbeat reports a newer version. 409 UP_TO_DATE if it's already on the latest release. Installs no longer show the deploy command.

Changed

  • The signature check for install requests is shared by the heartbeat and update requests.
  • docs/hub-protocol.md brought in line with the install's copy (licence states from Cross Events 1.41.1).

[1.0.1] - 2026-10-27

Changed

  • Renamed from Hope Events Hub to Cross Events Hub, following the rename of Hope Events to Cross Events. Page titles, alert emails and the authenticator-app label now say Cross Events. Protocol identifiers (hel1. licence tokens, CEH- licence keys) are unchanged, so existing installs and licences keep working.

Added

  • Logo in the sidebar and on the login page; favicon and Apple touch icon.

[1.0.0] - 2026-10-26

Added

  • Hub v1 (docs/hub-protocol.md, protocol 1):
    • Install API: public key, register (licence key → install id, secret and signed licence), heartbeat (HMAC-signed, 5-minute clock window) returning a fresh licence token.
    • Licence tokens signed with Ed25519, valid 30 days, carrying status, expiry, grace days and limits (AI cap for Cross Events 2.0).
    • Dashboard: installs with health, version (flagged when behind the latest release), licence and last heartbeat; install detail with health, usage, licence, history and notes.
    • Customers and licences: generate keys (CEH-XXXX-XXXX-XXXX-XXXX), set status (active / suspended / revoked), expiry, grace and AI cap, release a licence from a site.
    • Alerts every 5 minutes — offline, database, stale backup, low disk, errors, failing jobs, pending migrations, licence expiring/expired, behind latest — emailed once when they start.
    • Heartbeats kept 30 days, then one a day.
    • Login with two-factor (authenticator app) required, sign out everywhere, password change, audit log.
Reference in New Issue View Git Blame Copy Permalink