Run application in web /context-path (for reverse-proxying)
djechelon opened this issue · 2 comments
My request is to provide ability to run Matomo under a different /context-path than root.
Motivation is that we would like to must deploy several applications under the same https port on the load balancer, instead of dedicating a port to Matomo. My ITSM confirmed that they won't open anything but 443.
A lot of applications for Docker include the ability to deploy themselves under a different /context-path via properties.
I have not run yet Matomo as I am doing bill of materials at the moment. As Matomo will have to co-exist with other web applications on the same server, it would be preferrable to distinguish them by context path rather than port number.
Maybe this is already possible and my issue reduces itself to documenting that on the README.
Thank you for attention
@djechelon Did you find a solution for this issue? I have the same problem as well.
Only way was to use SNI (Server Name Identification) in https