fix(caddy): add /tiles/* routes so frontend can reach baked clutter tiles#464
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two routes to both Caddyfiles, ordered so
/tiles/*and/api/tiles/*match before the generic/api/*handler:handle /tiles/*— direct fetches whenVITE_API_BASE_URLis unset (frontend falls back towindow.location.origin).handle_path /api/tiles/* { rewrite * /tiles{uri} }— for deployments that setVITE_API_BASE_URL=/api. Tiles are mounted outside/v1on the API, so the rewrite strips/api/tilesand re-prefixes/tilesinstead of going through the generic/api/* → /v1/...rewrite some deployments use.