From fdfac1807b917f880e40dc9d506811439a19d444 Mon Sep 17 00:00:00 2001 From: larssand Date: Mon, 16 Nov 2026 17:46:01 +0100 Subject: [PATCH] add new features roadmap --- ROADMAP.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/ROADMAP.md b/ROADMAP.md index 950e569..62272c4 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1143,3 +1143,25 @@ On hold by the club operator. Needs an explicit go-ahead before building, since - [ ] When the finals are done and the race is linked to a House of RC event, the results notice offers **📤 Send to House of RC** (final results, same payload as the manual send), with ✅ or the error shown at once. After qualifying heats it can offer "Send qualifying results". - [ ] Never automatic: every send is a click. Double clicks don't send twice; a judging change after a send turns the button into "Results changed - send again". - [ ] No server or database change (`/api/houseofrc/results` exists). Test only against a fake House of RC server, never the real API. + +## RaceCore Hub: clubs publish to rcracecore.se (idea 2026-11-16, not started) + +Goal: a club registers on rcracecore.se, gets a token, and its RaceCore publishes races, the live schedule and results there, so drivers and parents can follow along from anywhere. House of RC stays the master for entries and results on House of RC; the Hub is an extra publication that the club turns on itself. + +Blueprint (agreed as an idea, needs a go-ahead before building): +- **Hub backend on the club operator's Synology:** a small Node service with SQLite in Container Manager (Docker). Web Station sends `/api/` to it; the rest of rcracecore.se stays static. Same language as RaceCore, so leaderboard and "My race today" logic can be reused. (Alternative: PHP + MariaDB, already on the NAS, but that means a second code base.) +- **Club account and token:** the club gets a token from the Hub, stored hashed there. In RaceCore it goes under Settings → System, kept server-side only like the House of RC key, never in `app_state`, exports or the browser. +- **What RaceCore sends:** the live schedule (reusing the snapshot `publishPublicRaceDay` already posts every 15 s), heat, qualifying and final results, classes and drivers with name, club and country only. Practice stats only for drivers who opted in. Never email, phone, emergency contact or age. +- **On the site:** a page per club (upcoming and running races, live schedule), results per race and class, and later a driver page. + +Phases: +- [ ] 1. Hub + club tokens handed out by hand (invite only). The site shows schedule and results. +- [ ] 2. Self-registration with email verification and approval by the operator. +- [ ] 3. Practice stats per driver with consent, and driver pages. + +To decide before phase 1: Node/SQLite in Docker or PHP/MariaDB; invite-only or open registration. + +Notes: +- GDPR: many drivers are children. Names in public results must be something the club turns on, with a way to hide a driver. +- The Hub is an internet-facing service on the NAS: rate limiting, writes only with a valid token, database backups. +- Separate from "House of RC: send results with one click" above, which stays on hold.