Nextcloud it will create…
Main it expects it to ALREADY EXIST as external is true
Every app on the nextcloud network which is every app in this stack can communicate with each other
Apache on the main network is there so it can be reached by the reverse proxy and we can access it, and ONLY it externally
***In the example no ports are published and the reverse proxy is used and everything on the nextcloud network has access to everything and every port on that and only that network
If you need access to these apps form the host and are not using a reverse proxy… add the ports to apps you are coming in on from the host
you dont have to create them in a single compose file. The apps just need to share a common network.
I have 20 apps with their own compose fiels which all share the common network “proxy”, so i can reach them via traefik and domain name.
Thanks for the help to both of you, can I create the external networks in a custom app (pasting the yaml) and “tell” an existing “iX App” (point and click) to use that network?
in a compose it is this simple to connect a container to it
networks:
main:
name: main
external: true
services:
flaresolverr:
networks:
- main
For an IX-AP I imagine there is a way to join an external network in the setup screen… I cant check it myself as I have my EE temp install offline until release
Yea, networking is something on our list to do for Apps. The trouble is exposing that in a way where you don’t break internal apps communication every time by mistake. That will start to be addressed after this lands: