Add support prefixPath for web UI #4013
JiffsMaverick
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
|
Can you use different ports? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I am also interested in this feature, and I went a little further in my attempts by supporting context path settings ( 0001-context-path-for-filer-ui.patch |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I use Seaweeds on one server. I use nginx to securely access web UI (master, volume, filer) using HTTP Basic Auth. I want to use one domain for this (I can't use subdomains), but in the current implementation, I can't do that. For example:
https://example.com/master - for master web UI
https://example.com/volume - for volume web UI
https://example.com/filer - for filer web UI
For my company, I made a hardcoded crutch in the code for this:
But it looks terrible :) I hope you find time to implement a more adequate implementation of this function.
P.S.: And if you could also make a main page from which you could get to all the others (master, volume, filer) - it would be awesome!
Beta Was this translation helpful? Give feedback.
All reactions