-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Please don't use ports
in docker-compose
#1
Comments
When I do that, I get '404 not found' on the first service and "Bad Gateway" on the second:
|
rfay
added a commit
to rfay/ddev-meilisearch
that referenced
this issue
Jan 27, 2024
kevinquillen
added a commit
that referenced
this issue
Feb 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Congratulations on this add-on! People have asked for this periodically for years.
You use
ports
in each of the stanzas of the docker-compose.This means that this add-on can only be used in one running project.
Instead, use
expose
, and HTTP_EXPOSE and HTTPS_EXPOSE environment variables to accomplish what you want.You can look at many other add-ons to see how this is done, or docs, see https://ddev.readthedocs.io/en/latest/users/extend/custom-compose-files/#docker-composeyaml-examples
The text was updated successfully, but these errors were encountered: