I can create a new subdomain and assign a Let’s encrypt cert to it, if that’s what you mean.
So a custom bridge network can use the host DNS for resolving external domains. Can the DNS + the hosts RP be used to access another container in the same bridge network (see image)?
Most probably not, as the RP resolves to localhost: but would need the CODE containers IP.
What if the CODE container runs in a separate bridge network?
usually you would place a reverse proxy in front of multiple service you host.. (many reasons exist).
Well, this is what I currently do with the hosts RP. At least I access different containers, but the shortcut is, what I don’t know how to do yet.
This one doesn’t have a link, or did you mean this one:
Because the second link is a bit vague, or at least I can’t depict a solution for it.
I checked other tutorials and guides, some include an nginx in their docker compose but it listens to 80 and 443 which is already used on the host, also an RP is already in place, handling the other containers and services on the host.
Other guides just use a domain for their docker container but don’t state how the domain is resolved or they don’t use a bridge network.