There's a lot of ways to use Vagrant. Some people create a virtual machine per project. I don't like that idea. I think it's best to create a virtual machine for each different server you have to deploy. So if I have 2 projects that are going to be deployed to the same server why should I create two virtual machines? Makes no sense to me. Those two projects belong in the same virtual machine.
As you may or may not know, I started to really use vagrant lately. The installation process to get a PHP development environment is quite easy. However, there was a few moment were I run into a small issues. Most of them happened just because my mind was still programmed to work with a simple Lamp stack.
One of the issues that made me lose 20 minutes or so was connecting SequelPro to the database. Sure I installed PHPmyAdmin but I wanted to use my own database management app.
Recently I wrote a post about my dev setup on mac. However someone has been recommending me for a while to start using Vagrant. But I never did. Specially because my dev setup was working fine.
A few days ago, I decided it was time to do a clean install on my mac, and start fresh. That means it's time for some experimenting.
Not yet. We still have time to look back. Yeah, it's that time of the year. Time to think back on what happened this last year. What went wrong and what went well.
Are you? If you are, this might interest you. I've been doing some consultant work where I'm basically putting Intranets to the test. Basically I'm the troll telling people what are they doing right or wrong.
So his is what I've found so far on things that you might want to avoid.