Request: config option to change static ui path prefix

[mcreekmore]

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.

[EnriqueL8]

I believe you can set PUBLIC_URL environment variable for this https://github.com/hyperledger/firefly-ui/blob/2011cffe7a8b5cb5a3485712950294780e672633/public/index.html#L8

[mcreekmore]

I believe you can set PUBLIC_URL environment variable for this https://github.com/hyperledger/firefly-ui/blob/2011cffe7a8b5cb5a3485712950294780e672633/public/index.html#L8

@EnriqueL8 I've tried this originally and it doesn't seem to work as expected. Static resources are still fetching from the root prefix

[EnriqueL8]

Correct @mcreekmore I think this is at build time only of the UI resources

[mcreekmore]

Correct @mcreekmore I think this is at build time only of the UI resources

@EnriqueL8 Forgive me I'm a bit confused now. The PUBLIC_URL variable is meant to resolve this issue, and yet its not possible to set the variable properly without rebuilding the container?

How is it possible to set the prefix for static UI resources while using the officially signed container?

[EnriqueL8]

Turns out the PUBLIC_URL variable is only usable when building the UI resources so yes would need to rebuild the resources.

So we would need to do the following:

• Make this path configurable in the FireFly API Server to host the UI resources

  firefly/internal/apiserver/server.go

  Lines 408 to 411 in 36b4179

  	uiPath := config.GetString(coreconfig.UIPath)
  	if uiPath != "" && config.GetBool(coreconfig.UIEnabled) {
  	r.PathPrefix(`/ui`).Handler(newStaticHandler(uiPath, "index.html", `/ui`))
  	}

• At runtime allow the static resources to requests at the correct path