11 ms·

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagr

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagrant configurations that I use to build different servers for local testing/debugging: https://github.com/geerlingguy/ansible-vagrant-examples https://github.com/geerlingguy/ansible-vagrant-examples There are plenty of other great examples of Vagrant usage around the web, too, from Laravel's Homestead to (disclosure, I maintain it) Drupal VM. It seems a lot of older applications / communities migrate towards Vagrant as some of the things they do are harder (or at least not as straightforward yet) to implement in containers.

neovive 9y ago
Homestead is wonderful! I've been using it for years for Laravel development. Thanks!
- Blaine0002 9y ago
  He meant Drupal VM :)
  - baby 9y ago
    I'll still add that Homestead and Laravel are amazing.
porkloin 9y ago
Thanks for all your hard work on DrupalVM, Jeff :)
ArlenBales 9y ago
> Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments) That's only a recent trend. Up until Docker became the standard a couple years ago (or whenever Docker for Mac was made stable), Vagrant was the standard for dev environments. The primary reason Docker succeeded Vagrant for dev environments is speed. Docker can have my dev environment up from scratch in seconds, but with Vagrant it took minutes.
- aidenn0 9y ago
  Also the early reliance on virtualbox was a performance issue for some build environments even once they were up. I have at least one C++ project that (for windows) takes 8x as long to build on vbox vs. a real machine.
  - TwelveNights 9y ago
    Wow, it doesn't rely on VirtualBox anymore? I remember using it before for the development environment of an old company, and that being a small nuisance. Nowadays, Docker is really miles ahead in terms of usage in development environments. Vagrant was pretty easy to set-up and use back then, but now Docker is much, much easier.
    - porker 9y ago
      I need to get into this Docker malarkey for dev machines. Running on Windows, how do you share files between the Docker image and the host machine? With Vagrant I use NFS.
      - h_r 9y ago
        You basically create a mount point inside the VM to a place on your host disk.
      - TwelveNights 9y ago
        To expand on the other commentor, check out volumes: https://docs.docker.com/engine/admin/volumes/volumes/ https://docs.docker.com/engine/admin/volumes/volumes/.
    - aidenn0 9y ago
      Vagrant calls the backends "providers." It ships with 4 providers IIRC (VirtualBox, Hyper-V, VMWare, Docker), and there are plugins for dozens of others (it's so large a list because there's one provider each for pretty much every cloud service out there, even ones I've never heard of). I think that VirtualBox and VMWare are the only two providers that work everywhere, unless docker runs on windows now.
epalmer 9y ago
I am the maintainer for a dev env for our team. We are on Mac OS X but we develop for RHEL so the vagrant image is centos. Building an image takes a few minutes but we love it. We will probably research docker in 2018.
coolguy1982 9y ago
We use Vagrant with docker containers inside running our web apps. Vagrant functions as a disposable virtual dev environment (on Mac) to do our docker development in linux and know everyone's machines are identical when developing for production. A new dev can just download our latest vagrant repo, vagrant up and it'll provision their development environment to be exactly as it should be. It doesn't have to be one or the other.
- deleted 9y ago
  [deleted]
kevindication 9y ago
Just wanted to drop a note to say thanks for your nicely done ansible recipes.
_ix 9y ago
When I started learning Ansible, I kept running into your stuff on the Ansible Galaxy [0]. Such a peculiar name, it stuck with me. Thanks very much for your contributions! Vagrant is probably the best way to go about learning automated configuration management with ansible, and especially Puppet. And I've never tried it myself, but I hear people setting up local OpenStacks with Vagrant, too. Not a bad way to get your feet wet. [0] https://galaxy.ansible.com/ https://galaxy.ansible.com/
616c 9y ago
Amazing, I was just using your templates for Packer PoC stuff at work today. Your Ansible, Packer, and Vagrant stuff is topnotch and a great cliffnotes for quick experimentation. Keep up the good work!
samuell 9y ago
For Go-users wanting a quick way to get a basic Vim setup with Fatih's awesome vim-go plugin [1], you might want to checkout https://github.com/samuell/devbox-golang https://github.com/samuell/devbox-golang (Just updated to Go 1.9). It is a little different from some other vagrant boxes in that it uses Ansible for provisioning. This means you can reasonable easy re-use the ansible roles (perhaps with some minor modifications) elsewhere too, like locally, or on some cloud image. [1] https://github.com/fatih/vim-go https://github.com/fatih/vim-go

neovive 9y ago

Homestead is wonderful! I've been using it for years for Laravel development. Thanks!

Blaine0002 9y ago
He meant Drupal VM :)
- baby 9y ago
  I'll still add that Homestead and Laravel are amazing.

porkloin 9y ago

Thanks for all your hard work on DrupalVM, Jeff :)

ArlenBales 9y ago

> Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments) That's only a recent trend. Up until Docker became the standard a couple years ago (or whenever Docker for Mac was made stable), Vagrant was the standard for dev environments. The primary reason Docker succeeded Vagrant for dev environments is speed. Docker can have my dev environment up from scratch in seconds, but with Vagrant it took minutes.

aidenn0 9y ago
Also the early reliance on virtualbox was a performance issue for some build environments even once they were up. I have at least one C++ project that (for windows) takes 8x as long to build on vbox vs. a real machine.
- TwelveNights 9y ago
  Wow, it doesn't rely on VirtualBox anymore? I remember using it before for the development environment of an old company, and that being a small nuisance. Nowadays, Docker is really miles ahead in terms of usage in development environments. Vagrant was pretty easy to set-up and use back then, but now Docker is much, much easier.
  - porker 9y ago
    I need to get into this Docker malarkey for dev machines. Running on Windows, how do you share files between the Docker image and the host machine? With Vagrant I use NFS.
    - h_r 9y ago
      You basically create a mount point inside the VM to a place on your host disk.
    - TwelveNights 9y ago
      To expand on the other commentor, check out volumes: https://docs.docker.com/engine/admin/volumes/volumes/ https://docs.docker.com/engine/admin/volumes/volumes/.
  - aidenn0 9y ago
    Vagrant calls the backends "providers." It ships with 4 providers IIRC (VirtualBox, Hyper-V, VMWare, Docker), and there are plugins for dozens of others (it's so large a list because there's one provider each for pretty much every cloud service out there, even ones I've never heard of). I think that VirtualBox and VMWare are the only two providers that work everywhere, unless docker runs on windows now.

epalmer 9y ago

I am the maintainer for a dev env for our team. We are on Mac OS X but we develop for RHEL so the vagrant image is centos. Building an image takes a few minutes but we love it. We will probably research docker in 2018.

coolguy1982 9y ago

We use Vagrant with docker containers inside running our web apps. Vagrant functions as a disposable virtual dev environment (on Mac) to do our docker development in linux and know everyone's machines are identical when developing for production. A new dev can just download our latest vagrant repo, vagrant up and it'll provision their development environment to be exactly as it should be. It doesn't have to be one or the other.

deleted 9y ago
[deleted]

kevindication 9y ago

Just wanted to drop a note to say thanks for your nicely done ansible recipes.

_ix 9y ago

When I started learning Ansible, I kept running into your stuff on the Ansible Galaxy [0]. Such a peculiar name, it stuck with me. Thanks very much for your contributions! Vagrant is probably the best way to go about learning automated configuration management with ansible, and especially Puppet. And I've never tried it myself, but I hear people setting up local OpenStacks with Vagrant, too. Not a bad way to get your feet wet. [0] https://galaxy.ansible.com/ https://galaxy.ansible.com/

616c 9y ago

Amazing, I was just using your templates for Packer PoC stuff at work today. Your Ansible, Packer, and Vagrant stuff is topnotch and a great cliffnotes for quick experimentation. Keep up the good work!

samuell 9y ago

For Go-users wanting a quick way to get a basic Vim setup with Fatih's awesome vim-go plugin [1], you might want to checkout https://github.com/samuell/devbox-golang https://github.com/samuell/devbox-golang (Just updated to Go 1.9). It is a little different from some other vagrant boxes in that it uses Ansible for provisioning. This means you can reasonable easy re-use the ansible roles (perhaps with some minor modifications) elsewhere too, like locally, or on some cloud image. [1] https://github.com/fatih/vim-go https://github.com/fatih/vim-go