Configuring Vagrant for Small Teams

Asked

Viewed 356 times

5

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

  • How I provide a Vagrant configuration for other developers to download and start a VM with the same configuration?
  • Is SSH access usually released to the developer? We use PHP and I would like to leave open to the developer to run command lines such as Composer and Artisan from Laravel.
  • If there is a need to install something that has an impact on the server configuration, as I update this in Vagrant provisioning, in a way that this update also occurs in other developers' Vms?

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

php vagrant

  • Hello Vineyards and welcome to [pt.so]. Can you post what you’ve already done? How far has it come? Otherwise your question will be too wide and will probably be closed.

  • Eae Vinhas, gives a read on this article. I needed to do the same last week and it was very good for beginners in the subject like me. http://flaviosilveira.com/2012/vagrant-facil-e-util/

  • Thank you Premiere! I will look at it calmly, I am orienting myself by another article also very good: (http://friendsofvagrant.github.io/v1/docs/getting-started/index.html). It’s a little outdated but you can already get a good idea of how it works

  • Since you are using Laravel: http://laravel.com/docs/homestead

  • @Caputo I needed for this project to give way to another. However, I intend to return the question soon :)

1 answer

1

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

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

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

The Puphpet can help you set up the machine with a cool GUI (in case you encounter difficulties setting up the machines).

Browser other questions tagged php vagrant

You are not signed in. Login or sign up in order to post.