I've been looking at mrsk as a more modern, cross platform and simpeler alternative to the likes of Deployer and Kubernetes. In order to use it, we need to move towards a production setup where the code is packaged inside docker containers as opposed to depending so heavily on docker-compose.yml.
So far, I've tackled the following:
Reworked the way packages are grouped in the container registry;
Moved back to a single docker-compose.yml file per environment. Which will only be used in development;
Made containers more configurable through ARG values that can be set at build time;
Added an alternative to bash's variable substitution to avoid packaging bash and use a single format for the ARG values, in both Ubuntu and Alpine.
To-do
[x] Besides replacing the dot, sed should also replace the last zero with nothing;
[x] Move as many container configuration values from docker-compose.yml to the containers themselves;
I've been looking at mrsk as a more modern, cross platform and simpeler alternative to the likes of Deployer and Kubernetes. In order to use it, we need to move towards a production setup where the code is packaged inside docker containers as opposed to depending so heavily on
docker-compose.yml.So far, I've tackled the following:
docker-compose.ymlfile per environment. Which will only be used in development;ARGvalues that can be set at build time;ARGvalues, in both Ubuntu and Alpine.To-do
docker-compose.ymlto the containers themselves;