So we need something that’s easy to use and will do most of the heavy lifting for us. Note that I won’t be covering CLI-based local dev environments in this article. We have another complete article covering Laravel Valet, VVV ( Vagrant), Chassis, etc. There are quite a few different applications and tools that fit this bill, but for now we’ll be comparing the four GUI-based tools that seem to me to be the largest players in this space: XAMPP, MAMP (Pro), DesktopServer, and Local. The major differences between MAMP, XAMPP, DesktopServer, and Local is the ability to manage multiple sites and ease of use. While Local and DesktopServer allow you to customize domain names for local sites, XAMPP and MAMP (unless you’re using Pro) don’t. If you’re looking for a free alternative, XAMPP and Local are clear choices here. The rest of the applications offer paid versions with more features. If you’re making use of WP-CLI in your daily workflow, you might dislike Local. You can’t directly just enter in the working directory and execute CLI commands. You’ll need to go through their application to open the SSH container separately for each site. I personally make use of WP-CLI on a daily basis and this is what’s keeping me from switching to Local completely from MAMP Pro. Let’s have a more in-depth look at these local WordPress development environments. XAMPP, which you may be surprised to find out is pronounced “Shamp”, is probably the oldest local development environment around and possibly the most complex. XAMPP stands for X-platform Apache MariaDB, PHP and Perl – It’s definitely the only local server that still touts Perl support as a major feature, so if you like to keep it TMTOWTDI, then this is definitely the one for you. Though you can also find the Perl command line tool optionally available in MAMP Pro. #CANNOT USE SQLITEMANAGER DOWNLOAD#Installing XAMPP seems easy enough: just download the correct installer from their website and run it. #AMPPS CANNOT USE SQLITEMANAGER DOWNLOAD# I first tried installing XAMPP under a new user on my Mac laptop. The installer ran fine but that’s about all it did. #CANNOT USE SQLITEMANAGER INSTALL#Once the install was complete and I found the app that I needed to run (hint for users of Alfred/Spotlight as app launchers: it’s not called “XAMPP”, it is intuitively called “Application Manager”), I couldn’t get the server to start up. #AMPPS CANNOT USE SQLITEMANAGER DOWNLOAD#.#AMPPS CANNOT USE SQLITEMANAGER INSTALL#.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |