3 ms·
Typically it's a good idea to separate build and testing phases strictly, exactly for these types of reasons. You deploy the same image to dev, testing and prod
by stingraycharles 9y ago
Typically it's a good idea to separate build and testing phases strictly, exactly for these types of reasons. You deploy the same image to dev, testing and production, and it becomes easy to reason about an artifact without confusing it with the environment it runs in.
I hope this helps.
- dankohn1 9y agoRight, but the point of my question is that deploying the same image to test, staging and production means that I'm necessarily using a less lean image, since I'm including gems only needed in development and test.
- kingbirdy 9y agoWhy do you have gems only needed in those envs?
- dankohn1 9y agoI'm trying to balance two conflicting goals in Docker: identical images in different stages and the leanest possible production images. My question is whether development and testing gems should be included in production or not.