Skip to content

Connect to ollebo.com with the map key and register maps - #12

Merged
mattiashem merged 1 commit into
mainfrom
connect-ollebo
Nov 7, 2026
Merged

mattiashem merged 1 commit into
mainfrom
connect-ollebo

Conversation

@mattiashem

Copy link
Copy Markdown
Contributor

Why

The Settings check sent the key to /api/v1, which ollebo.com never accepted, so it always showed Disconnected and maps never reached a Space.

What changed

  • Connection check: calls dw's new /api/selfhosted/self and shows which mapserver and Space the key belongs to. A wrong key, a missing key and an unreachable ollebo.com each get their own message.
  • New maps: registered in that Space as soon as they're built.
  • Saving Settings or rescanning: sends the public URL and every map already built. That covers maps made before a key was set, and updates tile URLs after the public URL changes.
  • Never blocks local work: a wrong key or ollebo.com being down only gets logged, and maps still build.
  • API default: now https://www.ollebo.com/api, without the /v1 that dw never served.

Stacked on #11, so merge that first; GitHub then retargets this PR to main.

Depends on

  • Ollebo/dw, branch mapserver-link: the /api/selfhosted API. Until that's deployed, this shows "Map key not accepted" and registers nothing.
  • Ollebo/ollebo-maps, branch selfhosted-tiles-cors: without it, the dash lists registered maps but the browser blocks their tiles.

Testing

I built this branch's image and ran it against dw's real /api/selfhosted routes and a Postgres with the new migration, all in Docker, with a fake key. All 17 checks passed:

  • With no key, the map builds locally, nothing is sent and the status says no key
  • With a wrong key, nothing is sent and the status says the key isn't accepted
  • With the right key, saving Settings registers the existing map and stores the public URL, and the status names the mapserver and Space
  • The stored map is private and ready, with no asset, both variants and its bounds
  • A newly built map is registered automatically
  • Changing the public URL updates the same rows (same mapid, no duplicates)
  • With dw down, maps still build and the status says it can't reach ollebo.com
  • The key never appears in the server log
  • Not tested against production or on a cluster. That needs the dw change deployed.

Still open

  • The Settings page still returns the key in its page source, and the UI has no login.
  • A map deleted on ollebo.com comes back on the next rescan or Settings save.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AwkBcZCmo27zHnnRnAcKiy

The Settings check called /api/v1 with the key, which ollebo.com never
accepted, so it always showed Disconnected. It now calls dw's new
/api/selfhosted API (Ollebo/dw branch mapserver-link) and shows which
mapserver and Space the key belongs to.

Finished maps are sent to that Space. Saving Settings or rescanning also
sends the public URL and every map already built, which covers maps made
before a key was set and updates tile URLs after the public URL changes.
ollebo.com being down or the key being wrong never stops a map from being
built locally.

The API default drops the /v1 that dw never served.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AwkBcZCmo27zHnnRnAcKiy
@mattiashem
mattiashem changed the base branch from chart-publish to main November 7, 2026 13:56
@mattiashem
mattiashem merged commit bccac70 into main Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants