Have you heard of Docker? I first heard this word a year ago. If you rely on Vagrant to manage local projects, I highly recommend the one virtual machine, many projects strategy adopted by Laravel Homestead. However, you regain local system resources and have less infrastructure to install and manage. You lose project isolation, and you can't customize your server software stack for each project. Laravel Homestead is a popular Vagrant box that uses this strategy. The logical solution is to run multiple projects on a single Vagrant virtual machine. I can't tell you how often I have seen this warning message when I have too many concurrent projects: This means each project runs atop a full virtual machine, and each virtual machine has a complete operating system that demands a large overhead in system resources (e.g., CPU, memory, and gigabytes of disk space).
However, Vagrant has one large downside- it implies hardware virtualization. Vagrant builds a local environment that is identical to the production environment.Vagrant provides the same software versions for each team member.Vagrant isolates project environments to avoid software conflicts.
This approach accomplishes three important things: Vagrant is, according to its official website, a tool to "create and configure light-weight, reproducible, and portable development environments." Basically, Vagrant helps me create and provision virtual machines with unique combinations of software and configuration customized for each of my projects. I've used Vagrant to manage local development servers for several years.
0 kommentar(er)
