This repository has been archived by the owner on Sep 17, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basically, I tease the existing docker-compose file into three parts, for the major services that need to run in production. In order to function, the env files need to specify all the required variables in the new yaml files. I will document this.
This isn't perfect. An alternative solution would be to build the component compose files "on-the-fly" by parsing the base compose YAML. That may be the evolution of this change, but I wanted to prove out the basic ECS deployment.
Comments very welcome. I don't think this is merge-worth just yet, so I am interested in thoughts from the SM maintainers.
Changes:
Todo: