Configuring Vagrant for Small Teams

Navigation
5

I have a small team of PHP developers and want to set up their development environment using Vagrant . However, I have some doubts.

  • How do I make a Vagrant configuration available so that other developers can download and start a VM with the same configuration?
  • Normally SSH access is released to the developer? We use PHP and I would like to let the developer run command lines, such as Laravel's Composer and Artisan.
  • If there is a need to install something that impacts the server configuration, how do I update this in Vagrant provisioning in a way that this update also occurs in the VMs of other developers?

Anyway, if anyone has had the experience of setting up a development environment using Vagrant for a small team of developers in a company, I'd like to know how you've done it. I searched a lot on the internet but did not find anything specific to my case, just teaching how to configure Vagrant on a local machine.

    
asked by anonymous 24.07.2014 / 16:13

1 answer

1

  • Item 1: I imagine you are using a version control mechanism, correct? You can place the configuration files inside the repository of your application. Whenever a member of the team clone the repository (or upgrade) will have the updated settings to work on.

  • Item 2: The vagrant ssh command allows the user to access the instance that is running SSH quietly.

  • Item 3: If you change any detail of the provisioning, you will update the configuration file which, according to my response to item 1, will be updated in your repository. When the other members of the team turn the machine on again the setting will be changed and everything will be synchronized.

PuPHPet can help you set up the machine with a legal GUI (if you encounter difficulties setting up machines).

    
26.11.2014 / 13:16
Different guidelines on your smartphone and tablet Recover MySql table