![]() ![]() Node, PHP, Rails, Static Sites, Vagrant could care less. The only reason I say Vagrant is a little step ahead of the other solutions is because you can run anything through it since it's just a virtual machine sitting on top of your OS. This helps and makes sure everyone is on the exact same environment developing with the exact same configuration, so no more problems having someone say they can't get it to work lol. It also works amazing for teams, since there is no configuration you need to do on your computer except download VirtualBox (free) and Vagrant (free). It is a little work to get setup the way you want for the specific environments you want it to build out, but saves many problems down the line and makes it worth it in the end. Works amazing and provides a super maintainable and quick workflow for getting a local dev environment to mimic your staging and production environments. Try this following link to upgrade to 5.5 Josegonzalez Homebrew PHP 5.5 - After about a year of doing it that way I finally discovered Vagrant. I switched from MAMP to using an upgraded version of apache, mysql and php 5.5 using homebrew. So, while I think a stand-alone Ubuntu box is the best way to go for PHP compatibility, MAMP Pro is as good as I can ask for on Mac.I used MAMP since the very humble beginnings of development. However, WSL with Ubuntu seems to be a good solution there, as Ubuntu has modules for installing PHP 5 (3rd party, but nerd-party, for sure). I haven't tried it there, and I hate using PHP on Windows anymore. My boss paid for it, and it's not expensive. Like, with anything I threw at it, PHP 5.4 to 8 (now 8.2 works just fine). MAMP Pro, when I tried it out, just worked. My boss and previous developers couldn't figure out why I was struggling, and it was difficult to explain that the things they used to install their versions years before were not available anymore. I was losing my mind, as Brew stopped supporting it. Ultimately it came down to guessing which sub-version of a library to compile to get something necessary working, and getting warnings about overwriting security files on the computer with outdated versions. I tried getting PHP 5 working on Catalina, and it was a nightmare. I've been using MAMP Pro on Mac for two years with PHP 5 through 8, and it was a savior. I really don't know why, as developers, we often shift to needlessly complicated solutions when there are simpler ones readily available. ![]() Two minutes later everything was working. I wasn't messing around with that when the two other current projects required the newer version. The solution was to delete the version of PHP I was using and relinking to an older version. Long story short, valet never grabbed the correct PHP version. But yesterday I had to switch PHP versions for a specific project and it opened up a whole can of worms. Then it was Laravel Valet, which I've been happily using for a few years. But losing a whole day because of an update gone bad put end to that experiment. you aren't a real dev unless you embrace the command line). Then, moved over to MAMP.Įventually I succumbed to the vagrant hype (e.g. I started with just running apache right from my Mac, but updates would always break the set-up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |