To maximize reuse of your codebase, and to ensure your developers work under the same environment, you want an easy way to share Vagrant Boxes within your team and across your organization. Distribute and share boxes across your organization This white paper presents the benefits of pointing your Vagrant client at Artifactory to replace Atlas as a source and target for Vagrant boxes in an enterprise software development organization.ġ. Vagrant does offer private boxes on Atlas, Vagrant’s repository in the cloud, but enterprises typically require a more secure environment for boxes in which the company’s source code may end up.Īrtifactory’s support for Vagrant means you can easily setup local repositories for Vagrant boxes.

Consequently, an organization needs to maintain and manage hundreds of boxes at a time.

Teams may have different requirements for the environment on which their project isīeing developed, and frequently, a version of the team’s source code may reside in a Vagrant box together with the infrastructure. But the question remains, what is the right box? A development organization may need many different boxes. Now, all a developer has to do is type vagrant up with the right box, and start coding within minutes. Since Vagrant joined the virtualization scene, these are problems of the past. These are exactly the issues that Vagrant solves. Configuring operating systems, databases, development workspaces and a host of cloud services can sometimes drag on for a hair-pulling week or more. But setting up a machine to be just like others can be a complex process. Any developer who has ever heard another developer say, “…but it works on my machine” understands this. Bugs stemming from differences in environment variables, versions of infrastructure and other causes that are extraneous to the code itself, are often the most difficult to track down and resolve.

The importance of a uniform development environment among team members can’t be understated.

Download vagrant box