Vacation status: playing with Dockerizing our @emberjs app setup so developers can have it Just Work
.
Yes, I’m that much of a nerd.
-
-
Yes! That’s actually the primary reason I’m doing this: I want my mostly-Windows, mostly not-front-end colleagues to be able to have our Ember app just spin up and go without their having to grok all the other bits and pieces.
-
how is this different from using https://www.vagrantup.com/ ? I assume on Win/OSX you still need some sort of VM to run the Docker containers, right?
-
Yep. The biggest wins from what I see so far: - the VM is abstracted away - you can have multiple containers sharing the same base VM, with their own app dependency setups (e.g. different Node versions), so it’s easier to make more bespoke but also *lighter* overall.
-
Tried this half a year ago, but gave up. For non-Linux hosts, this made more problems than it solved, at least for me. Docker for Mac was very slow due to slow file I/O of the locally mounted volume (known issue at that time, when working with *many* files, here npm and tmp)
-
Interesting. That’s good to know. I’m going to evaluate and see how it is now – I expect *some* improvements – and if it’s even semi-reasonable I think it’ll be a win for the “just spin it up, not developing it” scenario we sometimes have.
-
Yeah, my primary use case was to allow non-devs to just spin up a feature branch, but still the ember build was so slow I lost interest in this. There are workaround like http://docker-sync.io/ for Mac (which I use for some non-Ember setups), but this seemed even more overkill
-
Yeeeeesh. Here’s hoping it has since improved. (I’ll report back once I know for sure, probably sometime tomorrow. Need to get some volume mounts set up first.)
-
Please do that, would love to know if it makes sense to retry it myself! I quickly extracted our config (using docker-compose) into this gist, maybe this helps? https://gist.github.com/simonihmig/4d9531dc41a61e54ef1291f96546d26a …
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.