Skip to content
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

Distinguish between production and development docker images #1

Open
larribas opened this issue Nov 10, 2016 · 0 comments
Open

Distinguish between production and development docker images #1

larribas opened this issue Nov 10, 2016 · 0 comments

Comments

@larribas
Copy link

larribas commented Nov 10, 2016

As we did on the RENO project. You can basically copy it around I guess (if you decide to use Rocker), or use two different Dockerfiles.

The logic behind this is... from a purely prod environment, I don't need Node, NPM, or any of the node_modules to be installed, right? I only need the dist/ folder contents. And then, my image goes from 400MB+ to 20MB+, and so the memory footprint of the containers is lower (and we get to pay less for DigitalOcean, if we need to scale out!).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant