I'm starting to study Vagrant with Chef and I've come to realize that it's great for a development environment, making life a lot easier when it's well set up, but it does not create a safe enough environment to be reproduced in production, At least I have not found ways to make it safe in production yet. What I want to know is if it is possible and what should I do to maintain 100% similarity between my development, test and production environments and still enjoy the facilities of Vagrant and Chef?
How to use Vagrant or Packer in the production environment?
4
asked by anonymous 14.02.2014 / 18:02
1 answer
1
Honestly, I think the use of vagrant and more for homomlogging, given the issue of security, organization (disk partitioning) of so, hardering and the use of virtualisation (bare metal) as the provider of virtualbox. I like sysadmin, I use more to generate a simulation of the production scenario, running via vagrant 3-6 vms with different operating systems as it is in production, according to the project. So I can change some question, be it in the interconnection, or versions and etc, that I know will run in production, and to actually deploy to production, I use docker. So, in the case of the vagrant, we use the docker that isolates only the application (the file) and play to the server in production without any compatibility problems.
03.04.2015 / 19:37