We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there support/guides for multiple docker-compose projects? e.g. something like:
# server/docker-compose.yml services: caddy-gen: ... networks: [caddy-gen] networks: {caddy-gen: {name: caddy-gen}} # project1/docker-compose.yml networks: {caddy-gen: {external: true}} services: app1: labels: {virtual.host: app1.domain.com} ... # project2/docker-compose.yml networks: {caddy-gen: {external: true}} services: app2: labels: {virtual.host: app2.domain.com} ...
This is useful to keep different unrelated projects in different repos.
Is putting everything on the same network sufficient for caddy-gen to pick up other services?
network
caddy-gen
Obviously there won't be any depends-on entries in this case. Are there any other caveats?
depends-on
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there support/guides for multiple docker-compose projects? e.g. something like:
This is useful to keep different unrelated projects in different repos.
Is putting everything on the same
network
sufficient forcaddy-gen
to pick up other services?Obviously there won't be any
depends-on
entries in this case. Are there any other caveats?The text was updated successfully, but these errors were encountered: