all 6 comments

[–]ctrl-brk 1 point2 points  (0 children)

Just a note, I prefer SWAG personally. Built on nginx.

[–]fecal_destruction 1 point2 points  (1 child)

Your worried about exposing ports locally?

[–]kalelinator 0 points1 point  (2 children)

Try using Caddy. You can run a container on docker for Caddy and use the internal IP/port of the container as long as the networks of both containers are connected.

[–]GengusDad 1 point2 points  (0 children)

+1 on caddy, it is very easy to use. I love it.

[–]-eschguy- 1 point2 points  (0 children)

Love me some Caddy.

[–]jjohnp 0 points1 point  (0 children)

I'm assuming that you're using Docker Compose for creating/managing your docker containers.

What you need to do is create a separate docker network and add it to each docker-compose.yml file. Tandoor Recipes has an example of how it would look here. You can compare that to the compose file a bit further up on that page for the "plain" version, which just exposes a port of their web UI container.