Installing WordPress on a local server environment is fairly straight forward. On a Mac the local Apache server may report Error 404 Object not found! errors as it attempts to serve WordPress posts and pages.
These errors can often be attributed to the use of pretty permalinks in WordPress. Stopping them from occurring can be achieved by a simple amendment to the Apache server’s configuration file.
Having MAMP’s Apache and MYSQL servers start at login is as simple as checking the Start Servers when starting MAMP option in MAMP’s preferences and adding MAMP.app to the Login Items.
However, some user intervention is needed if using the standard ports for Apache: 80 and MySQL: 3306 instead of MAMP’s default ports. In this case MAMP will require a password when it starts as port 80 is a privileged port.
I have several computers on my local network each with a local server environment provided by XAMPP. As it stands, the local server on each computer can only serve pages stored on that machine.
If I have a local site on computer A that I wish to access on computer B I have to replicate that site’s entire folder structure on computer B and on all other computers I want to access the site from.
An important feature of MAMP is an option to have the Apache and MySQL servers started as the application opens. Include MAMP as a Login Item and the MAMP servers are up-and-running after login.
XAMPP has no such option. Including XAMPP as a Login Item merely opens the XAMPP Control.app and the servers have to be started manually.
The answer is to a use a daemon.
The application MAMP provides a local server environment for your Mac separate to the one installed as default by OS X.
Both the premium and free versions of MAMP provide a single localhost, but unlike the paid version, the free one does not provide a nice interface to configure virtual hosts.
Configuring virtual hosts in the free version of MAMP has to be done manually.