Closed ghost closed 4 years ago
Hi,
So you create an additional "appnetwork" and connect trafik plus your db and app container to it. No need for another frontend network.
You may look at the https://github.com/ReinerNippes/selfhosted_on_docker playbook which creates one internal network for each app and connects trafik to this app network.
Also, for self-signed certs to be used. Do I just leave ssl_cert_email
?
EDIT: I ask these questions about the networking as I want to deploy Taiga
most likely using a modified version of this docker-compose.yml
I believe even for letsencrypt the email address is not necessary. It's only to send you a reminder before the certificate would expire. In case the automatic renewal would work.
If you put the taiga and postgres container on the backend network everything would be fine. To access taiga you would have to add tags to the container so traefik will route traffic to the container.
If you use portainer you'll have a web gui to your docker environment.
I believe even for letsencrypt the email address is not necessary. It's only to send you a reminder before the certificate would expire. In case the automatic renewal would work.
If you put the taiga and postgres container on the backend network everything would be fine. To access taiga you would have to add tags to the container so traefik will route traffic to the container.
If you use portainer you'll have a web gui to your docker environment.
I would also need to put taiga on the frontend network as well correct?
Sorry this is kind of going out of scope of my original question. Really appriciate the help.
No. Only traefik is connected to the frontend network. Since it is also connected to the backend it acts as a reverse proxy for the taiga container.
Many thanks for your help @ReinerNippes!
Hi 👋🏻 Thanks for the awesome playbook. I have some questions.
Many thanks!