-
Notifications
You must be signed in to change notification settings - Fork 17
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
Allow an app's .terra.yml file to override or extend the generated docker-compose.yml #21
Comments
I'd suggest just using the We'd still need the option of setting it in the |
First use case was to add a container linked to the app container, I've successfully added code to do this:
Because we need to always link these addon services to the app container, I called the property There's still more work to do to allow apps to totally override their docker setup. I welcome others to help on this, as it's not a priority for me at this point. |
I was reminded recently that docker doesn't require microservices. One might as well run everything in one container. Which might be a bit of an advantage if one's using containers designed to be as close to an existing production environment as possible. Maybe the concept of environment templates is something that'll be needed at some point? |
Absolutely. I'd like the EnvironmentFactory to be completely swappable actually, so users wouldn't even have to use docker. Just needs work to get there. The flip side is, that I'd like for the default to be scalable. Once you are locked into a single container, it's hard to get out. |
I've gotten this working for attaching services to the app container automatically. It is not able to fully override docker-compose yet. See https://github.com/terra-ops/terra-app/blob/master/docs/.terra.yml#L29 for an example .terra.yml |
The .terra.yml file could have something like this
or
which would automatically merge with the generated compose.yml file.
Feedback welcome.
The text was updated successfully, but these errors were encountered: