c4874dc04c
The interim proxy (#239/#240/#242/#243) covers the day-one needs for Overpass — User-Agent compliance via server-side proxy, same-origin + rate limit + cache with coalescing, bbox quantization, observability. Further work on self-hosting the upstream is no longer urgent. Move the full OpenSpec artifact set out of openspec/changes/ so it doesn't clutter the active change list, and park it under docs/ideas/self-host-overpass/ as a reference for when we revive it. Adds a short README at the new location capturing: - current interim solution - triggers that would justify reviving (rate limits, >1 req/s, etc.) - key decisions already made (Hetzner-to-Hetzner firewall model, DOCKER-USER chain, capacity ceiling at DACH on current box) - how to switch when the time comes (flip OVERPASS_URL, no client changes) The files were never committed in the first place (WIP in the working tree through the proposal session), so no git history to preserve. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
52 lines
2.5 KiB
Markdown
52 lines
2.5 KiB
Markdown
# self-host-overpass (parked)
|
||
|
||
Full OpenSpec artifact set (`proposal.md`, `design.md`, `specs/`, `tasks.md`)
|
||
for hosting our own Overpass API. Moved here from `openspec/changes/` so it
|
||
does not clutter the active change list; revive by moving the directory back
|
||
under `openspec/changes/` when ready to implement.
|
||
|
||
## Status
|
||
|
||
**Parked.** The interim proxy work (`/api/overpass` → `overpass.private.coffee`,
|
||
see `apps/planner/app/routes/api.overpass.ts`) covers the day-one needs:
|
||
User-Agent compliance, same-origin check, rate limiting, server-side cache
|
||
with coalescing, bbox quantization, Grafana observability. That buys us time
|
||
before we need to own the upstream.
|
||
|
||
## When to revive
|
||
|
||
Revisit once **any** of these is true:
|
||
|
||
- private.coffee rate-limits our traffic or changes policy
|
||
- Our query volume makes continued use of a free public instance feel like
|
||
abuse (rule of thumb: >1 req/s sustained)
|
||
- We want POI coverage outside regions private.coffee happens to import
|
||
- Privacy posture requires full control of the upstream
|
||
|
||
## Key decisions already made
|
||
|
||
- **Topology**: Overpass runs on the maintainer's second Hetzner box
|
||
(FSN1, dedicated, i7-2600, 32 GB, 2×3 TB HDD, 1.8 TB free). Both hosts
|
||
share Hetzner's internal backbone with ~1 ms RTT.
|
||
- **Access control**: host-level firewall via nftables `DOCKER-USER` chain
|
||
(Docker bypasses `INPUT` when publishing ports, which is the classic
|
||
gotcha). Only the Planner host's egress IP is allowed on the Overpass
|
||
port. Planner host IP lives in `/etc/overpass/planner-ip.env` on the
|
||
Overpass box, **not** in the repo. Tailscale / WireGuard / vSwitch kept
|
||
as future hardening options.
|
||
- **Capacity ceiling on current hardware**: DACH extract fits comfortably
|
||
in the 23 GB of RAM available on the Overpass box. Europe+ would need
|
||
different hardware (AX52 ≈ €54/mo for a dedicated 64 GB NVMe box that
|
||
handles planet at low user counts; see design.md).
|
||
- **Switch path**: no client changes needed to cut over — the Planner
|
||
proxy already reads `OVERPASS_URL` from env and defaults to
|
||
private.coffee. Flipping the env var points at our own instance.
|
||
|
||
## What's in the folder
|
||
|
||
- `proposal.md` — why / what / impact
|
||
- `design.md` — topology, firewall pattern, capacity analysis, risks
|
||
- `specs/` — delta specs (would land against `overpass-hosting`,
|
||
`osm-poi-overlays`, `infrastructure`, `rate-limiting`)
|
||
- `tasks.md` — 10 groups of implementation tasks
|
||
- `.openspec.yaml` — OpenSpec scaffolding; keep for when it comes back
|