You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the viewer sits at the root of the server. Other than something like the /metrics or /capabilities, you cannot not route to it.
While I love the viewer for debugging, I don't want just everybody to use it - so I don't want to exclude it from the build either.
There's currently an option to prefix the entire webserver, but that would only shift the root to the new prefix, with my issue persisting still.
Do you think it makes sense to optionally add a prefix for the viewer specifically? So it can live with e.g. /viewer, can be used internally but doesn't have to be exposed publicly.
The text was updated successfully, but these errors were encountered:
There has been a request to be able to host /metrics on a different port/prefix as well. If we were to do this, I think it would make sense for both /metrics and /viewer to have the functionality.
I don't see any issue with this request. I just think we should consider first time UX. We want the user to get to "Ah ha" quickly, and they can do that by hitting localhost:9090. With this change the user would need to hit localhost:9090/viewer. Not a huge deal, but something to consider.
Hi there 👋
Right now the viewer sits at the root of the server. Other than something like the
/metrics
or/capabilities
, you cannot not route to it.While I love the viewer for debugging, I don't want just everybody to use it - so I don't want to exclude it from the build either.
There's currently an option to
prefix
the entire webserver, but that would only shift the root to the new prefix, with my issue persisting still.Do you think it makes sense to optionally add a prefix for the viewer specifically? So it can live with e.g.
/viewer
, can be used internally but doesn't have to be exposed publicly.The text was updated successfully, but these errors were encountered: