{"id":1371,"date":"2009-02-23T09:00:10","date_gmt":"2009-02-23T09:00:10","guid":{"rendered":"http:\/\/www.markwilson.co.uk\/blog\/2009\/02\/installing-wordpress-on-a-mac.htm"},"modified":"2009-02-23T09:00:46","modified_gmt":"2009-02-23T09:00:46","slug":"installing-wordpress-on-a-mac","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2009\/02\/installing-wordpress-on-a-mac.htm","title":{"rendered":"Installing WordPress on a Mac"},"content":{"rendered":"

The software platform which markwilson.it runs on is in desperate need of an updated but there is only me to make it happen (supported by ascomi<\/a>) and if I make a mistake then it may take some time for me to get the site back online (time which I don’t have!). As a result, I really needed a development version of the site to work with.<\/p>\n

I thought that it would also be handy if that development version of the site would run offline – i.e. if it were served from a web server on one of my computers. I could run Windows, IIS (or Apache), MySQL and PHP but as the live site runs on CentOS, Apache, MySQL and PHP it makes sense to at least use something similar and my Mac fits the bill nicely, as a default installation of OS X already includes Apache and PHP.<\/p>\n

I should note that there are alternative stacks available for running a web server on a Mac (MAMP<\/a> and XAMPP<\/a> are examples); however my machine is not a full web server serving hundreds of users, it’s a development workstation serving one user, so the built in tools should be fine. The rest of this post explains what I did to get WordPress 2.7 up and running on OS X 10.5.5.<\/p>\n

    \n
  1. Open the System Preferences and select the Sharing pane, then enable Web Access.<\/li>\n

    \"Web<\/p>\n

  2. Test access by browsing to the default Apache website at http:\/\/computername<\/em>\/<\/code> and a personal site at http:\/\/computername<\/em>\/~username<\/em>\/<\/code>.<\/li>\n
  3. Download the latest version of MySQL Community Server<\/a> (I used mysql-5.1.31-osx10.5-x86_64) and run the corresponding packaged installer (for me that was mysql-5.1.31-osx10.5-x86_64.pkg<\/code>).<\/li>\n
  4. After the MySQL installation is completed, copy MySQL.PreferencePane to \/Library\/PreferencePanes and verify that it is visible in System Preferences (in the Other group).<\/li>\n

    \"MySQL<\/p>\n

  5. Launch the MySQL preference pane and start MySQL Server (if prompted by the firewall to allow mysqld to allow incoming connections, allow this). Optionally, select automatic startup for MySQL.<\/li>\n

    \"MySQL<\/p>\n

  6. Optionally, add \/usr\/local\/mysql\/bin<\/code> to the path (I didn’t do this, as creating a .profile file containing export PATH=\"$PATH:\/usr\/local\/mysql\/bin\"<\/code> seemed to mess up my path somehow – it just means that I need to specify the full path when running mysql commands) and test access to MySQL by running \/usr\/local\/mysql\/bin\/mysql<\/code>.<\/li>\n
  7. Enable PHP by editing \/etc\/apache2\/httpd.conf (e.g. by running sudo nano \/etc\/apache2\/httpd.conf<\/code>) to remove the #<\/code> in front of LoadModule php5_module libexec\/apache2\/libphp5.so<\/code>.<\/li>\n
  8. Test the PHP configuration by creating a text file named phpinfo.php containing <?php phpinfo(); ?><\/code> and browse to http:\/\/localhost\/~username<\/em>\/phpinfo<\/code>.<\/li>\n
  9. With Mac OS X, Apache, MySQL and PHP enabled, start to work on the configuration by by running \/usr\/local\/mysql\/bin\/mysql<\/code> and entering the following commands to secure MySQL:
    \ndrop database test;
    \ndelete from mysql.user where user = '';
    \nflush privileges;
    \nset password for root@localhost = password('{newrootpassword<\/em>}');
    \nset password for root@127.0.0.1 = password('{newrootpassword<\/em>}');
    \nset password for 'root'@'{hostname<\/em>}.local' = password('{newrootpassword<\/em>}');
    \nquit<\/code><\/li>\n
  10. Test access to MySQL. using the new password with \/usr\/local\/mysql\/bin\/mysql -u root -p<\/code> and entering newrootpassword<\/em> when prompted.<\/li>\n
  11. Whilst still logged in to MySQL, enter the following commands to create a database for WordPress and grant permissions (I’m not convinced that all of these commands are required and I do not know what foo is!):
    \ncreate database wpdatabasename<\/em>;
    \ngrant all privileges on wpdatabasename<\/em>.* to wpuser@localhost identified by 'foo';
    \nset password for wpuser@localhost = old_password('wppassword<\/em>');
    \nquit<\/code><\/li>\n
  12. Download the latest version of WordPress<\/a> and extract it to ~username\/Sites\/ (i chose to put my copy in a subfolder called blog, as it is on the live site).<\/li>\n
  13. Configure WordPress to use the database created earlier by copying wordpressdirectory<\/em>\/wp_config_sample.php to wordpressdirectory<\/em>wp_config.php and editing the following lines:
    \ndefine('DB_NAME', 'wpdatabasename<\/em>');
    \ndefine('DB_USER', 'wpuser');
    \ndefine('DB_PASSWORD', 'wppassword<\/em>');
    \ndefine('DB_HOST', 'localhost:\/tmp\/mysql.sock');<\/code><\/li>\n
  14. Restart Apache using sudo apachectl restart<\/code>.<\/li>\n
  15. If WordPress is running in it’s own subdirectory<\/a>, copy wordpressdirectory<\/em>\/index.php and wordpressdirectory<\/em>\/.htaccess to ~\/Sites\/ and then edit index.php so that WordPress can locate it’s environment and templates (require('.\/wordpressdirectory<\/em>\/wp-blog-header.php');<\/code>).<\/li>\n
  16. Browse to http:\/\/localhost\/~username<\/em>\/wordpressdirectory<\/em>\/wp-admin\/install.php<\/code> and follow the “five minute WordPress installation process”.<\/li>\n

    \"WordPress<\/p>\n

  17. After installation, the dashboard for the new WordPress site should be available at http:\/\/localhost\/~username<\/em>\/wordpressdirectory<\/em>\/wp-admin\/<\/code>.<\/li>\n

    \"WordPress<\/p>\n

  18. The site may be accessed at http:\/\/localhost\/~username<\/em>\/wordpressdirectory<\/em>\/<\/code>.<\/li>\n

    \"WordPress\n<\/ol>\n

    Credits<\/h3>\n

    I found the following articles extremely useful whilst I was researching this post:<\/p>\n