-
Is there a way to configure Orbstack to allow containers defined in my docker-compose to communicate with each other using the *.orb.local domains? I'm working on a headless WordPress project with a Next.js frontend. I'd like for clientside requests and Node.js to both be able to communicate back to WordPress using the same domain (https://admin.thrive.orb.local/). I've resorted to adding a caddy container and setting up aliases for it in the docker-compose and installing the caddy root cert in the WordPress container, but it would be nice if Orbstack could handle all this itself. This seems to be related to https://github.com/orgs/orbstack/discussions/982 but isn't quite the same. I believe I was able to work around the issue there by adding a mu-plugin for local dev that forces |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This is already supported, but we don't provide automatic HTTPS for container-to-container connections. Subscribe to #1159 for updates. |
Beta Was this translation helpful? Give feedback.
This is already supported, but we don't provide automatic HTTPS for container-to-container connections. Subscribe to #1159 for updates.