One script for installing, updating and moving church installs, replacing hope-events' scripts/deploy.sh and install.sh: - deploy <church> [events] / --every-church, with --version, --main, --check and --allow-local-changes: checks every product first (files changed by hand, Node, release requirements from WHATS-NEW.md headings), then each product in order with backup, checkout, install, migrate, build, PM2 reload and a /health version check; a failure rolls that product back and stops. - status [<church>]: checked-out and latest release, /health, and the old folder kept after adopt. - install <church> --products events --domain <address>: a new church under /var/www/sites/<church>, writing church.env. - adopt <church> --events-dir <old> builds the monorepo checkout next to the running install and switches PM2 over; adopt --undo goes back to it. Product hooks live in scripts/products/events.sh. shellcheck (lint:scripts) and 47 bats tests (test:scripts) are part of npm run check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.2 KiB
5.2 KiB
Handover — Cross Code, all products
Last updated: 2026-11-12. The plan is ROADMAP-v3.md (decided 2026-11-03,
decisions table near the end). This file says where each phase stands and what comes next.
Product-specific notes (where the code lives, known gaps) stay with each product: Cross Events'
are in hope-events/docs/HANDOVER.md (apps/events/docs/HANDOVER.md from Events 2.2.0), and
the Hub's are in events-hub/docs/.
The docs for every product are here in docs/: the roadmap, the Hub protocol
(hub-protocol.md, with a copy in events-hub), this handover and the plans
for each phase. They moved here from hope-events/docs/ on 2026-11-05.
Repos
| Repo | What |
|---|---|
joshua/crosscode-platform (this one) |
Contracts, the apps (Accounts, Website, App, and Events from 2.2.0), shared packages, the crosscode script (from Events 2.2.0), the server agent (apps/agent, phase 1d), and these docs |
joshua/hope-events |
Cross Events up to 2.1.x. Archived after the 2.2.0 move |
joshua/events-hub |
Cross Code Hub. Its own server, its own scripts/deploy.sh |
joshua/crosscode-site |
crosscode.co.za. Updated at the end of every phase that changes what it says (ROADMAP §9) |
Where each phase stands (ROADMAP §9)
| Phase | What | State |
|---|---|---|
| 0 | contracts 1.0.0 / 1.1.0 | Released 2026-11-04 (contracts@1.0.0, contracts@1.1.0). Not published to a registry (decision 22): the Hub gets a packed release committed to its repo |
| 1 | Hub 2.0.0 | Released 2026-11-05 (events-hub v2.0.0; docs/HUB-2.0-PLAN.md there). Not deployed yet: events-hub/deployment.md → "Upgrading to 2.0" (run check-hub2 first). crosscode-site's address prices are merged, not deployed yet |
| 1b | Cross Events 2.2.0: moves here as apps/events, crosscode script |
In progress. Planned in EVENTS-2.2-PLAN.md. Steps 1–3 done 2026-11-12 (merged into main): history merged in under apps/events (from hope-events e6c9670), workspaces and one root lockfile with versions pinned to 2.1.1, same test results as 2.1.1 (711 backend tests, typecheck, both builds). The crosscode script and adopt (§4–5) are written (branch feat/crosscode-script, 2026-11-12; shellcheck and 47 bats tests pass, not yet run on a server). Still to do: VM testing (§6), the version bump and events@2.2.0 tag, adopting each install, archiving hope-events (§7). Until then servers keep deploying from hope-events v2.1.1, and Events work happens here (hope-events is frozen; a hotfix there as 2.1.2 is cherry-picked into apps/events) |
| 1c | Cross Events 2.3.0: authenticator app 2FA (TOTP + recovery codes) | Not started (TwoFactorMethod enum in Events' prisma/schema.prisma) |
| 1d | Agent 1.0.0 + Hub 2.1.0 (+ contracts 1.2.0): server agent, installs / scheduled updates / uninstalls from the Hub, server stats | Planned 2026-11-12 in AGENT-1.0-PLAN.md (ROADMAP decisions 27–37). Starts after 1b; can run alongside 1c |
| 2 | Cross Events 2.4.0: protocol v2, Linked products, event feed, packages/seo |
Not started. Events keeps speaking protocol 1 until then |
| 3–7 | Accounts 1.0.0 → Website 1.0.0 → Events 3.0.0 → App 1.0.0 → App 1.x | Not started |
Next up
- Deploy Hub 2.0.0 and crosscode-site (the address prices). This finishes phase 1 and is
needed before 2.2.0, because Hub 1.7 can't see
events@…tags. - Cross Events 2.2.0: EVENTS-2.2-PLAN.md. Decided 2026-11-05:
adoptbuilds next to the running install and switches over, andadopt --undois built (ROADMAP decisions 25–26). - Agent 1.0.0 + Hub 2.1.0 (phase 1d): AGENT-1.0-PLAN.md. Before the
first install through it: check
proxy_bind_addr = 127.0.0.1infrps.inion the central server (worth doing now: without it, tunnel ports such as:5000may be reachable straight from the internet), and set each server's database settings andTRUST_PROXYin the Hub. - Cross Events 2.3.0 (authenticator app 2FA), then 2.4.0, as in ROADMAP §9.
Things to remember across phases
- Before selling the Website or App: put the ROADMAP §10 prices in
crosscode-site/src/data/pricing.mjsand the Hub'sfrontend/src/lib/tiers.ts(plusbackend/src/utils/billing/tiers.js) in the same phase, so the site and the Hub never disagree. - A phase isn't done until crosscode-site matches it (ROADMAP §9, "Updating crosscode-site").
- Servers stay PM2 + nginx (no Docker), with one database per product per church, under
/var/www/sites/<church>/<product>. - Prisma in the monorepo: each app other than Events sets its own generator
output, so hoisted clients don't overwrite each other (EVENTS-2.2-PLAN §2). - AI for a church: set the licence's monthly AI cap above R0 on the Hub; with no cap the buttons don't show (rules in Events' handover, "AI rules").
- Releasing: branch → merge → tag (
<product>@<version>) → push, with a CHANGELOG entry, andnpm run checkfirst. Pushes to c-git often fail authentication the first time; retry once.