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
{{ message }}
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
I would like to use haproxy in rancher instead of nginx, so instead of mapping container to host ports directly in compose, I expose the container ports internally, and then I can use haproxy to map the ports on a per-domain basis.
I also run letsencrypt and haproxy uses the cert generated exclusively. so I would prefer to get rid of nginx altogether and not let any mailu container have access to the cert private keys.
is what I described here doable?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to use haproxy in rancher instead of nginx, so instead of mapping container to host ports directly in compose, I expose the container ports internally, and then I can use haproxy to map the ports on a per-domain basis.
I also run letsencrypt and haproxy uses the cert generated exclusively. so I would prefer to get rid of nginx altogether and not let any mailu container have access to the cert private keys.
is what I described here doable?
The text was updated successfully, but these errors were encountered: