![]() ![]() I should have been getting real work done. The hours of lost time trying to troubleshoot were astounding, even for someone who loves to waste time troubleshooting. Without knowing exactly what I was doing, I’d try reprovisioning, or halting and restarting, and sometimes re-installing the entire thing. Some mornings Vagrant simply wouldn’t load, or I’d get an SSH timeout error. I certainly did that a bit in the beginning, without knowing what or why. If you talk to a developer who’s used Vagrant long enough, they’ll tell you a time or two they’ve screwed it up somehow. MAMP is not perfect, and is certainly a PITA to update, but getting it up and running is as easy as 1. Too bad it took me heavy parts of multiple days to do so. I quickly added Variable VVV and a VVV Dashboard I was off and running with a shiny new development environment. I’ll admit it was pretty exciting to type that first (successful) Vagrant up in Terminal and see a default WordPress site sitting there. I’m not sure what went wrong the first couple of tries. Tore down and tried a third time – wha-la – I guess third times are a charm. Tore it all down and tried again – nothing. While most tutorials on how to set up Vagrant / VVV show how clearly easy it is, my experience was anything but… I followed along installing the necessary components and ran my first Vagrant up – and nothing. But matching dev environments is the first reason on most Why Vagrant articles, and I just took it away. MAMP doesn’t allow for much configuration either, so perhaps this is a draw. As long as the server is hitting the WordPress minimum requirements, maybe it doesn’t matter. I still to this day don’t know if a site would run differently on PHP 5.5 vs 5.6. The differences between environments never actually crossed my mind, because it never seemed to actually matter. Perhaps I should have, but every WordPress site I’ve built has worked fine no matter what production environment they ended up in. ![]() It also comes with the ability to alter that configuration, but I never took the time to do so. VVV is a Vagrant configuration specifically designed for WordPress and comes with a default configuration. In practice, however, I don’t really need this. One of the most compelling arguments for switching to Vagrant is that it allows a developer to set up a virtual environment that matches exactly the final production server configurations. Matching development and production environments Well, a few months ago I switched back to MAMP Pro. But hey, it’s the price of progress I thought. Yes, Vagrant took a long time to launch every morning, and even longer to shut down at night. While the initial setup wasn’t as smooth they said it would be, I was very excited to be learning some new tricks, using the command line, and being part of, well, the cool developer crowd. ![]() After (quite a) few initial hiccups, I had a Vagrant environment up and running, with VVV to manage WordPress. My Twitter feed was overflowing with Vagrant awesomeness and tutorials on how to set it up. Quite a few influential developers were making the switch. At the time it was the trendy thing to do, and still is I’d presume. Like a lot of folks, a few years back I switched my local WordPress development environment from MAMP Pro to Vagrant / VVV. Especially learning new development tools. Yes, it can be overwhelming, but for me it is also rewarding. New code specifications, design trends, device capabilities, programming languages, API integrations… Wait, did I say rewarding? One of the most rewarding things about web development is that it’s always changing. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |