-
-
Notifications
You must be signed in to change notification settings - Fork 458
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
Using a different context path than root #80
Comments
For documentation purpose: It is possible to change the base URL/context path with the environment variable There is a Change base URL section in the REAMDE file. |
This was referenced Jul 9, 2023
Closed
HeinrichAD
pushed a commit
to HeinrichAD/plantuml-server
that referenced
this issue
Jul 19, 2023
The "special" value of `ROOT` will serve requests on `/`. Any other value should serve on `/$BASE_URL` (as long as there are no slashes in `BASE_URL` at least). The default has been set to `plantuml` to better match documentation in the README.md file. Re plantuml#80, may help with plantuml#79.
HeinrichAD
pushed a commit
to HeinrichAD/plantuml-server
that referenced
this issue
Jul 19, 2023
The "special" value of `ROOT` will serve requests on `/`. Any other value should serve on `/$BASE_URL` (as long as there are no slashes in `BASE_URL` at least). The default has been set to `plantuml` to better match documentation in the README.md file. Re plantuml#80, may help with plantuml#79.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I was trying to run the server on a different path than root, but since the the .war file was named ROOT.war it was impossible for me. I have changed this so now is possible to do it at build time like this:
docker image build --build-arg context_path=name_of_dot_war_file -t plantuml-server .
This is was my solution:
This is obiviously not the best solution since I can't run the server on for example /my/context/path, just in /my_context_path
I think that this was supported before d7a8a7e
Thank you for your help!
The text was updated successfully, but these errors were encountered: