Installing XAMPP seems easy enough: just download the correct installer from their website and run it. Though you can also find the Perl command line tool optionally available in MAMP Pro. 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.
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. Let’s have a more in-depth look at these local WordPress development environments. 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. You’ll need to go through their application to open the SSH container separately for each site. You can’t directly just enter in the working directory and execute CLI commands.
If you’re making use of WP-CLI in your daily workflow, you might dislike Local. The rest of the applications offer paid versions with more features. If you’re looking for a free alternative, XAMPP and Local are clear choices here. While Local and DesktopServer allow you to customize domain names for local sites, XAMPP and MAMP (unless you’re using Pro) don’t. The major differences between MAMP, XAMPP, DesktopServer, and Local is the ability to manage multiple sites and ease of use. 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. We have another complete article covering Laravel Valet, VVV ( Vagrant), Chassis, etc. Note that I won’t be covering CLI-based local dev environments in this article. So we need something that’s easy to use and will do most of the heavy lifting for us.
0 kommentar(er)
