4 ms·

Yep, I don't get this whole trend. Want to start a virtual machine? Use docker-machine. Want to start a bunch of services? Use docker-compose. Want to define th

Yep, I don't get this whole trend. Want to start a virtual machine? Use docker-machine. Want to start a bunch of services? Use docker-compose. Want to define the service stack? Use a Dockerfile with the predefined language stacks. Previously we used to write hundreds of lines of puppet/chef/whatever scripts just to set things up. Its all already boiled down to just a few lines of configuration files. With tools like this or otto, its getting further hidden into nothing, seeming to look almost like magic. I'd rather stick with the few lines that I can control.

tylerflint 11y ago
Yes, nanobox will try to auto-configure your environment for you. If you would rather define your environment or if nanobox can't auto-configure your environment, you can either: 1- Explicitly define your app's environment with the Boxfile (https://docs.nanobox.io/getting-started/boxfile/ https://docs.nanobox.io/getting-started/boxfile/) 2- Write your own engine that will actually setup the environment (https://desktop.nanobox.io/engine-dev/ https://desktop.nanobox.io/engine-dev/).