-
When setting up a reverse proxy (like Nginx Proxy Manager) in Docker container, not on the host, one of the most recommended patterns is to create a separate network for frontend, and then separate isolated backend networks for each of the services. Since nextcloud already has the Apache container as the front facing entity, it'll be cleaner to connect just the nextcloud-aio-apache container to the frontend network, and keep all the nextcloud AIO maintained containers into the internal To that end, there should be an option to specify an additional external network that apache container should connect to. Here's the first cut implementation which I've tested locally: I can generate the PR but first wanted to open the discussion on whether this is the right way, since I'm very new to php. There will be some documentation update needed, which I can add when creating the PR. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi, thanks for reaching out regarding this. My suggestion would be that you create the PR and we do further discussion in there. Best would be if you could already provide the update to the documentation directly within the PR. Thanks a lot! :) |
Beta Was this translation helpful? Give feedback.
Hi, thanks for reaching out regarding this.
My suggestion would be that you create the PR and we do further discussion in there.
Best would be if you could already provide the update to the documentation directly within the PR.
Thanks a lot! :)