We want to use Vagrant for testing in our company. We also want to create a
company Vagrant box repository.
>From what I have been able to find this far, it seems like a web server and
catalogs json's for box versioning is the best option.
Are there any best practices or guidelines when it
hello
your mileage may vary.
You can host in atlas public boxes for free
paid boxes, please send an email to sa...@hashicorp.com to discuss.
To build boxes you can package using vagrant, or build using packer.
If you want to host your own versioning, and you already have the boxes,
have look
So, thats an important bit.
Vagrant is for development boxes.
You can use differnt providers, ie libvirt for qemu/kvm.
If your boxes wont be development, and you need some sort of SLA around
them, then I think will be better evaluate other tools too.
Vagrant can create VMs, and leave them
On Thursday 16 Feb 2017 at 20:49, Alvaro Miranda Aguilera wrote:
> So, thats an important bit.
>
> Vagrant is for development boxes.
Okay
But - development isn't an end in itself - things get developed so they can be
used in production, so if you use Vagrant for development, how do you
