Use multi stage Docker builds about meteor-now

[jkrup]

@leo and @qualitymanifest I've started a branch locally to use multi-stage builds to help reduce the ultimate docker image size. Unfortunately the build time goes up somewhat substantially with the current approach, so I'll probably default for it to be off (for those using a paid tier of ∆now) and you'll need to pass a flag like meteor-now -m(--multistage)

[qualitymanifest]

Came here because I'm having this problem. My app which had previously deployed fine many times is now getting this error. Apparently this limit is not new - I found this comment from a staff member on zeit's slack channel:

we’ve always had this restriction, however we have implemented more checks for limits recently so they might have just started being enacted for your account

Also, yes, thank you very much for creating meteor-now! It's been incredibly useful for me.

[bmackio]

I have successfully deployed a meteor app to now using their example app as a guide (https://github.com/zeit/now-examples/tree/master/node-meteor) which employs alpine.

The final size is 51MB. No error and I'm using cloud: v2

edit: actually, it works without the .dockerignore file

[qualitymanifest]

Cool! I'll keep my eyes peeled for the release. As for whether or not to have multistage builds be the default - from what I understand, the 100MB limit is not lifted with the paid plans. Per an email I got from Sergio at Zeit:

We limited the final built image to 100MiB in all plans.

I imagine most (all?) meteor projects are going to be over 100MB, so you might want to do it the other way around, and have a flag for non-multistage builds.

[bmackio]

@jkrup For reference, here's an example @TooTallNate sent us for a meteor deploy using multi-stage deploy: https://github.com/zeit/now-examples/pull/49