6 Commits

Include renames

Author	SHA1	Message	Date
randy	c66ae8d2d0	Fix kiwix ZIM volume mount to work with a symlink ... Bind-mounting data/kiwix/ (the directory) meant a symlink placed inside it broke: the container has to resolve that symlink itself, in its own filesystem, where the host path it points to doesn't exist. Binding the exact data/kiwix/wikipedia.zim file path instead resolves it on the host at mount time (plain mount(2) semantics), so the real ZIM can live anywhere on the host without duplicating a multi-GB file into this repo's data/ directory.	2026-09-09 14:01:39 +02:00
randy	24ac5931f8	Link POI popups to offline Wikipedia via kiwix-serve ... lib/maptool/kiwix.rb: a small reachability check for an external kiwix-serve instance. GET /api/kiwix reports it (same optional- integration pattern as offline-tiles/terrain-tiles); the frontend adds a "Nearby on Wikipedia" link to a point's popup pointing straight at kiwix-serve's own geo search (GET /search?latitude=&longitude= &distance=, confirmed from libkiwix's actual source rather than guessed) — linked to directly, not proxied/embedded, since it already has a full search UI of its own. docker-compose.yaml: new `kiwix` service (ghcr.io/kiwix/kiwix-serve) on the default network, KIWIX_URL wired to reach it by service name. The ZIM itself isn't part of the repo (large, self-contained archive) — data/kiwix/ gitignored same as the *.pmtiles files, setup steps in docs/development.adoc. No kiwix-serve/ZIM available here to test end-to-end — verified the app side against a stand-in local HTTP server (GET /api/kiwix flips available correctly) and confirmed the generated popup link matches the real geo-search query shape. docker-compose.yaml validated with `docker-compose config`. Full test suite: 118 runs, 0 failures.	2026-09-09 13:44:37 +02:00
randy	3e81ee8015	Run the GNSS simulator in production too ... Adds a gnss-simulator service to docker-compose.yaml, sharing maptool's network namespace (network_mode: "service:maptool") so it's reachable at the 127.0.0.1:2947 GpsdClient hardcodes -- there's no real receiver attached to the server, so without this the "GNSS" control there always shows "no fix". Both services now reference the same image (maptool:latest) explicitly rather than each service with its own `build: .` producing two separately-tagged (if identically-layered) images. Verified for real: built and ran the full compose stack in an isolated project/port on cube (not the live one), confirmed /api/gnss/position reports a moving fix across two polls through the actual sidecar networking, then tore it down completely -- containers, image, network, temp checkout. Production's own stack was untouched throughout and confirmed still healthy afterward.	2026-09-08 00:33:44 +02:00
randy	f9ddf860ea	Add Garmin LiveTrack session tracking ... A Gmail-watching Apps Script (documented in docs/deployment.adoc) posts the session ID from each LiveTrack email to a new webhook, which stores it in data/livetrack.json; a new sidebar panel lists what's been received.	2026-09-06 21:05:35 +02:00
randy	e13d1a1e97	Require Gitea login to write GPX data; IPv6-capable bind ... Upload/delete/move/create-folder now require logging in via Gitea OAuth2 (only MAPTOOL_ALLOWED_GITEA_USER is granted write access); reading stays public. Deploy secrets (session secret, OAuth2 client credentials, allowed user) are written to .env from Gitea Actions repo secrets on every deploy instead of living on the server by hand. Also switch the container's bind address to "[::]" (dual-stack) so the app is reachable over IPv6, not just IPv4.	2026-08-27 18:02:37 +02:00
randy	3a79c3d6c1	Add Docker deployment via Gitea Actions host-mode runner ... Containerize the app (Dockerfile, docker-compose.yaml) and add a CI deploy job that syncs the checkout to /srv/docker/maptool and runs docker compose directly, using the runner's new "host" execution label to reach the host's Docker daemon and filesystem.	2026-08-27 14:54:21 +02:00