3 ms·

This looks very interesting. I would love to be able to setup a workflow on my Windows machine that allows me to be able to do Rails dev on the Windows machine

This looks very interesting. I would love to be able to setup a workflow on my Windows machine that allows me to be able to do Rails dev on the Windows machine, in as close to a native way as possible - but with using much of the same workflow I use on my MBP. If I setup a container on my Windows machine, I would have still have to SSH into some virtual environment to be able to run my rails app, right? Ideally, I would love to be able to just go to my localhost in my browser and see my app - will this help me be able to do that, rather than going to a browser within a VM or some 'contained environment'?

rurounijones 13y ago
Docker looks like it is *nix only. It CAN be run on windows and Mac...inside a VM, which kind of eliminates all the advantages they talk about. An option is Vagrant (Which Docker uses on the above OSes) + chef / puppet. It uses VMs but works well enough for me and both configuration engines have widespread support. http://docs-v1.vagrantup.com/v1/docs/getting-started/ http://docs-v1.vagrantup.com/v1/docs/getting-started/
- marcamillion 13y ago
  I hate the small delays of a VM environment though. Rails already has some minor loading issues, adding a VM to that can be very frustrating - I imagine.
- shykes 13y ago
  Running docker inside doesn't eliminate all the advantages. For example, you can test a full stack of components (frontend, database, memcache, background workers...) on a single VM, instead of deploying 1 vm per component, which gets really heavy really fast. Another advantage is that docker on a vm is still docker: the container running on your local VM is 100% identical, bute-for-byte, to the container you will run on an octo-core box with half a tera of ram.
- krakensden 13y ago
  Not *nix only, Linux only. Solaris and FreeBSD have totally different container mechanisms, which honestly are probably better understood and vetted at this point than the LXC approach.
driverdan 13y ago
You want Vagrant[1]. It provides an easy way to control local headless VMs. It will mount local directories and port forward to your localhost. [1]: http://www.vagrantup.com/ http://www.vagrantup.com/
- marcamillion 13y ago
  I have been looking at Vagrant for a while - but it seems like just another VM packaging system to me. Am I mistaken, or will my Rails environment not sit in a VM in a Vagrant instance?
  - rurounijones 13y ago
    It will sit in a VM. Vagrant creates a VirtualBox (default) VM, uses chef / puppet (preferably) to set the environment up then you link the host's rails directory to a suitable location on the VM. So yes, the environment is a VM, you can use "vagrant ssh" to access that VM easily enough but for coding you use your usual code directory on the host with your usual editor.

rurounijones 13y ago

Docker looks like it is *nix only. It CAN be run on windows and Mac...inside a VM, which kind of eliminates all the advantages they talk about. An option is Vagrant (Which Docker uses on the above OSes) + chef / puppet. It uses VMs but works well enough for me and both configuration engines have widespread support. http://docs-v1.vagrantup.com/v1/docs/getting-started/ http://docs-v1.vagrantup.com/v1/docs/getting-started/

marcamillion 13y ago
I hate the small delays of a VM environment though. Rails already has some minor loading issues, adding a VM to that can be very frustrating - I imagine.
shykes 13y ago
Running docker inside doesn't eliminate all the advantages. For example, you can test a full stack of components (frontend, database, memcache, background workers...) on a single VM, instead of deploying 1 vm per component, which gets really heavy really fast. Another advantage is that docker on a vm is still docker: the container running on your local VM is 100% identical, bute-for-byte, to the container you will run on an octo-core box with half a tera of ram.
krakensden 13y ago
Not *nix only, Linux only. Solaris and FreeBSD have totally different container mechanisms, which honestly are probably better understood and vetted at this point than the LXC approach.

driverdan 13y ago

You want Vagrant[1]. It provides an easy way to control local headless VMs. It will mount local directories and port forward to your localhost. [1]: http://www.vagrantup.com/ http://www.vagrantup.com/

marcamillion 13y ago
I have been looking at Vagrant for a while - but it seems like just another VM packaging system to me. Am I mistaken, or will my Rails environment not sit in a VM in a Vagrant instance?
- rurounijones 13y ago
  It will sit in a VM. Vagrant creates a VirtualBox (default) VM, uses chef / puppet (preferably) to set the environment up then you link the host's rails directory to a suitable location on the VM. So yes, the environment is a VM, you can use "vagrant ssh" to access that VM easily enough but for coding you use your usual code directory on the host with your usual editor.