-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support serving Tiled from a sub-path. #283
Comments
A common use case for this is combining tiled with other services and UI apps behind a single reverse proxy server (nginx, k8s ingress nginx, traefik, etc.) Say you had a user interface that accessed tiled for some or all of its data. You would want several routes that your reverse proxy server could use for dispatching requests:
This is really difficult to do today, because tiled can only process requests to It would be better if we could configure the root path that tiled responds to. |
For Future Us, remember this comment suggesting a way forward here: #347 (comment) |
Addressed by #646 but needs docs. A working nginx config is over in bluesky/bluesky-pods#37. |
To be fair, #646 just makes it possible to configure the whole thing to sit behind nginx with no extra re-writing. The thing it does not do is move the |
I'm now confused. With #646, can I somehow mount all of tiled to, say, |
The ui is at |
And is |
yes. With the right nginx config (and a second tiled instance) you could even have |
Config, lifted from bluesky/bluesky-pods#37:
|
should probably use |
No description provided.
The text was updated successfully, but these errors were encountered: