3 ms·
My background: I’m a technical person who can get around Unix/Linux, work with file permissions, shell, databases, etc., comfortably. Yet, I have to agree with
by AnonHP 6y ago
My background: I’m a technical person who can get around Unix/Linux, work with file permissions, shell, databases, etc., comfortably. Yet, I have to agree with the author and her observations, especially after my trials on macOS.
> Here’s what I know now: running WordPress locally is a nightmare. Successfully figuring it out was way harder than it should have been.
I tried XAMPP recently after a long, long time (this is on Mac). After the initial steps of creating a database (not a problem for me), the database users and modifying wp-config.php, I faced all the errors the author writes about and more, and had to search online for solutions. Updating WordPress core fails due to permission issues. Cannot install plugins or themes from the dashboard because of permission issues. Heck, even uploading media files, like photos for example, for a WordPress post requires permissions to be handled. Even the location where the site is stored has to be mounted first if you’d like to explore, modify files, etc. Don’t even get me started on the black box that is ProFTPD to configure FTP access to the site (neither the ProFTPD site nor the StackExchange Q&A sites were very helpful)!
All this would be forgivable if the documentation was adequate. But I found the XAMPP site’s documentation to be really thin and sparse. One would think that the most popular blogging engine (WordPress) would be included in the documentation. But no, they just wash their hands of by pointing to Bitnami for installing apps, and that didn’t work for me either.
I can understand the XAMPP team focusing only on the basics, but the project has been around for a very long time and should cater to what most users may be using it for.
I recall that XAMPP (and the Bitnami stack) used to be easier to work with. Or maybe my memory of it isn’t good enough.
I also tried MAMP and gave up within minutes (forget about the free trial of MAMP Pro and upgrading to it).
All in all, XAMPP was a total disappointment and a very frustrating experience. I can only deeply empathize with the author who doesn’t seem to have as much exposure to dealing with systems at a lower level as I’ve had.
Right now, I would discourage anyone from trying XAMPP and MAMP (both on Mac; I don’t know if they’re vastly better on Windows or Linux). Just go with an online host with a good control panel and stop wasting your time.
- mdu96 6y agoHaha, I feel seen. Thanks for your comment. Wish someone would have warned me away from XAMPP and MAMP before I went to all the trouble!
- mjrpes 6y agoFor Windows folks, now that Window 10 WSL2 has been released, running Wordpress locally in something like Ubuntu seems like a better way to go. I find the drawbacks to WSL2 is that (1) there's no one-click GUI that will install Ubuntu + Wordpress; console commands are still required. It's still a virtual container, so network/file access isn't directly accessible like you get with XAMPP. There was an issue where webservers hosted inside WSL2 were not available on localhost, but that looks to be resolved and should hopefully be available to everyone soon: https://github.com/microsoft/WSL/issues/5298 https://github.com/microsoft/WSL/issues/5298 You could also install Docker inside WSL2 and run a WordPress image. However, wrapping your head around Docker poses its own challenges. Tutorials for Docker + Windows aren't really up to speed with WSL2 and troubleshooting often gives out-of-date advice. For instance PHPStorm Wordpress + Docker tutorials have files mounts from Windows into the container, which gives poor performance. However, I did have luck getting WordPress up and running on my local machine in Docker following this guide: https://www.singularaspect.com/phpstorm-using-xdebug-for-wordpress-development-in-docker/ https://www.singularaspect.com/phpstorm-using-xdebug-for-wor...