Is it possible to completely rebuild and click on the docker image every time you deploy, if you deploy 5-10 times a day?
I acknowledge the benefits mentioned in CircleCI Continuous Integration and Delivery with Docker , namely:
Note that Elastic Beanstalk also allows you to deploy the Dockerfile and its associated source code instead of the inline image, but by pre-creating the image on CircleCI and doing some form of validation on it, you can more determinate deployments as you delete the build environment as a variable that different between dough and production.
However, our fully constructed webapp image is close to 1 GB when all dependencies and source code are included. I just don’t understand how practical it is to deploy up to 200 GB / month (i.e. 10 commits daily, constantly deployed) when almost 99% of them do not change between assemblies. those. it can be as little as 1 kilogram of HTML, JS or CSS that has been modified to add features. I would prefer an approach in which the docker image contains rarely changing software, and the rest is fastened as part of the package. This will still lead to the creation of a standalone deployment file (without additional dependencies requiring downloads), but significantly reduce build time and throughput.