-
Notifications
You must be signed in to change not 8000 ification settings - Fork 226
Request: config option to change static ui path prefix #1679
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
Comments
I believe you can set |
@EnriqueL8 I've tried this originally and it doesn't seem to work as expected. Static resources are still fetching from the root prefix |
Correct @mcreekmore I think this is at build time only of the UI resources |
@EnriqueL8 Forgive me I'm a bit confused now. The How is it possible to set the prefix for static UI resources while using the officially signed container? |
Turns out the So we would need to do the following:
|
What would you like to be added?
Add an option such as
ui.prefix
to the firefly-core config options here:https://hyperledger.github.io/firefly/latest/reference/config/#ui
Why is this needed?
The Firefly UI (easily accessibly via http://firefly:5000/ui) is not accessible once its put behind a reverse proxy with a path prefix.
For example if it was necessary to access the ui behind https://example.com/firefly/ui, the browser would make requests to static resources without the
/firefly
path prefix resulting in 404s at https://example.com/ui/static/js/main.js.A configuration option that allowed you to either provide the entire FQDN+prefix or just the path prefix where the service sits would solve this problem. I was hoping that
api.publicURL
config option would serve this purpose but it does not.It may not be possible for all users to place the firefly ui/service directly at the root prefix.
The text was updated successfully, but these errors were encountered: