How to deal with ingress version ? #17
alexandrecuer
started this conversation in
technical facts
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ingress can work out of home assistant
HTTP headers
cf https://en.wikipedia.org/wiki/List_of_HTTP_header_fields
ingress use case
Suppose you have a sort of supervisor to manage configuration files and to view the containers logs
You want emoncms to be accessible in the supervisor user interface.
The solution is to use a reverse proxy listening on port 443, exposed to the outside as port 3443.
The web application operating in ingress mode will rewrite the emoncms urls, for example,
https://localhost:8099/vis/listwill becomehttps://localhost:3443/obm/emoncms/vis/list. The proxy will decode the rewriten urls and route them internally to the web application and vice versa.nginx reverse proxy
Here is a nginx.conf file :
Please note that trailing slashes are fundamental : cf https://stackoverflow.com/questions/58452321/nginx-reverse-proxy-everything-after-location-specification
It will not work if you use
/obm/emoncmsinstead of/obm/emoncms/andhttp://themis:8099instead ofhttp://themis:8099/the nginx container acting as the reverse proxy runs the following parameters :
apache reverse proxy
something similar can be achieved with apache.
For an alpine server running apache2, to install the proxy tools :
apk add apache2-proxyIn the virtualhost on port 8099
notes
https://www.nginx.com/resources/wiki/start/topics/examples/likeapache/
Beta Was this translation helpful? Give feedback.
All reactions