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
It is common that services like Sharry are hosted on a local server, and accessed through a reverse-proxy publicly available.
As I have several services (and cannot have sub-domains), I address each of them through a sub-path in the url, like :
As it is mentioned in the config file, this is not currently supported since the app will redirect navigator to http://public-ip/app, breaking the sub-path reversed proxy :
# Note: Currently deploying behind a path is not supported. The URL
# should not end in a slash.
This ticket is for adding support of deployment in sub-path url.
The text was updated successfully, but these errors were encountered:
It is common that services like Sharry are hosted on a local server, and accessed through a reverse-proxy publicly available.
As I have several services (and cannot have sub-domains), I address each of them through a sub-path in the url, like :
As it is mentioned in the config file, this is not currently supported since the app will redirect navigator to http://public-ip/app, breaking the sub-path reversed proxy :
This ticket is for adding support of deployment in sub-path url.
The text was updated successfully, but these errors were encountered: