EpicRide, the desktop client
EpicRide is the browser client for the work you would rather not do on a phone: planning a route properly, editing a track, writing up a trip. It runs at epicride.fastgis.eu and talks to the same API as everything else.
:::caution Being written This page describes what the client is and how it is put together. Screen-by-screen walkthroughs are still to come. :::
How it fits together
EpicRide is a single-page app in front of its own small gateway, which sits between the browser and the FastGIS API rather than the browser calling the API directly. The gateway holds the session, so an API key never reaches the page.
The gateway is configured by the DESKTOP_GW_* variables — DESKTOP_GW_UPSTREAM
names the API it proxies to, DESKTOP_GW_REDIS_URL holds its sessions,
DESKTOP_GW_SECRET_KEY signs them. It answers GET /healthz with
{"ok":true,"service":"desktop-gateway"}.
What it does
| Area | What you get |
|---|---|
| Plan | Build a route leg by leg, with an elevation strip and profile chart alongside the map |
| Modes | Switch the routing character — the same start and finish, ridden differently |
| Library | Everything you have recorded, imported or derived, with per-item pages |
| Sketch and vector tools | Draw and edit geometry, then save it back |
| Roadbook | Generate tulip-diagram pacenotes from a track |
| Stories | Author and publish trip stories and StoryMaps |
| Social | Friends, shared items and the leaderboard |
| Garage | Your motorcycles and riding styles, shared with the rider app |
| Support | An in-app chat backed by the support bot |
Anything you save is the same record the rider app sees — the library, the garage and your routes are one dataset, not a desktop copy.
Signing in
Sign in through the gateway with the same account you use everywhere else. The
gateway sets its own session cookie; DESKTOP_GW_COOKIE_SECURE should stay on
anywhere with TLS.