-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
feat: relative path support #1162
Comments
I also have the same problem. |
If not officially supported, but I can see that being useful for a lot of people. Feel free to make a PR! |
This can be accomplished through reverse-proxy and request rewrite rules as well. |
nope, i deployed it behind a reverse proxy but static files needs to be compiled with basepath too |
no, the proxy is not useful. the static files path is hard code. |
Use caddy2, Caddyfile config
It seems browser can fetch javascript static files, but get a runtime error:
|
I've successfully deployed an instance behind a reverse proxy from a subdirectory using the branch attached to #1701. I wouldn't say that I am particularly happy with the way how I solved it, but perhaps this is useful to whoever decides to work on a proper implementation. 😄 |
The feature was critical for me. I have implemented it there: The path is set dynamically when launching the container (variable). I will had a documentation if there are people asking for it. The MR was rejected. I will keep that fork up to date from time to time with only that feature for the next few weeks at least. |
I am interested @lmorin-inria!
It is able to rewrite most of the calls, but not all as it seems: |
You are welcome. The container I propose does not need any rewriting. That's the point, Sveltes uses a single page design template, and does not support URL rewriting. I fix this by configuring at runtime the "path" location. However I can see that in your configuration you try to rewrite the path. You should not probably. => When you launch the container, set the "ROOT_PATH" : In you case your might use that syntax : And the web server will serve the frontend pages in The backend answer to |
Bug Report
webui docker images do not support relative path.
Description
for xample, i want to start webui at localhost:8080/webui/, does the image parameter support the relative path configuration?
The text was updated successfully, but these errors were encountered: