iris-web
iris-web copied to clipboard
[FR] Option to skip nginx container
Please ensure your feature request is not already on the roadmap or associated with an issue. This can be checked here. ✅
Is your feature request related to a problem? Please describe.
For our server we need to modify docker-compose.base.yml
, which wouldn't persist updates.
We are using a server with Plesk where websites are accessible through a ready Nginx reverse proxy. The attempt to connect Nginx to the nginx
container failed (The plain HTTP request was sent to HTTPS port
) and having two Nginx reverse proxies in series doesn't give any additional value. The solution was actually to add a port to the app
container, to let Nginx on the host server connect there directly, and to disable the unused nginx
container. Added in docker-compose.base.yml
:
app:
ports:
- "127.0.0.1:<exposed port>:8000"
Describe the solution you'd like
This option could be implemented as a new variable in .env
that would let you disable the nginx
container and expose a port directly from app
. The port number could be taken from INTERFACE_HTTPS_PORT
or the value of the new variable.
It seems reasonable to offer also a minimal deployment option that avoids duplication, while keeping the current turnkey solution as a default.
Describe alternatives you've considered Alternatives would be to edit the yaml file after every update, to connect the two reverse proxies in series or to move to a different host server.