Developer documentation

Technical reference for the people building and running TogoActive. If you are setting up an event rather than changing code, you want the organiser guide instead.

The system in one picture

Four applications, two pairs, one database. The database is the integration — the admin side writes configuration, the WL side reads it. The only direct call between them is the domain sync.

Read in this order

New to the codebase? This sequence gets you productive fastest:

1. The four codebases — what each repository is, where it runs, which one to change.
2. How the admin works — a request through the admin pair.
3. How the WL side works — a request through the public pair.
4. Domain resolution — how one deployment serves every event on its own domain. Read this one even if you skip the others; it explains the single most surprising thing about the system.
5. End-to-end flows — registration, payment, activity sync and donation traced across every layer.
6. Then the service doc for whatever you are touching.

The services

Doc	Covers
Admin frontend	React + Vite admin panel served at v3.togoactive.com
Admin backend API	Laravel API behind /api on the same host
WL API	The white-label public API
WL frontend	The Next.js public event sites
Legacy app and TGP	The original Laravel app and the Togoparts integration

Data and infrastructure

• Database schema — tables, relationships, and the conventions that are not obvious from the column names.
• WL multi-version hosting — how a domain is pinned to a product version, and what the WL host is responsible for.
• Sync engine v2 — the ground-up rebuild of the Strava-to-leaderboard pipeline.

Check the date

Pages in this section carry a "last updated" stamp at the bottom. The platform moves faster than the prose does — where a doc and the code disagree, the code is right. If you find a gap, use the Suggest a change to this page link at the bottom of any page.