42f4c98014
The planner is the BRouter client in this architecture — route compute, rate limiting, and the eventual move of BRouter off-box all live there. The journal had two places that called BRouter directly (demo-bot and /api/v1/routes/compute) and both were broken on prod because the journal service has no BROUTER_URL. Fix: - Extend the planner's /api/route with an optional `format: "gpx"` that returns BRouter's raw GPX (for server-to-server callers that don't need the way-tag enriched GeoJSON). - Point the journal demo-bot at `PLANNER_URL/api/route` with `format: "gpx"` instead of calling BRouter directly. - Point /api/v1/routes/compute at `PLANNER_URL/api/route` instead of BRouter directly. Journal no longer needs BROUTER_URL at all. When BRouter moves to a dedicated host later, only the planner changes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api.overpass.ts | ||
| api.route.ts | ||
| api.sessions.ts | ||
| home.tsx | ||
| new.tsx | ||
| session.$id.tsx | ||