Project

General

Profile

Actions

RedmineInstallOSX » History » Revision 2

« Previous | Revision 2/9 (diff) | Next »
Bevan Rudge, 2010-08-24 05:05
Finishing instructions for installing Redmine on Mac OS X (not-Server edition)


Installing Redmine on Mac OS X 10.6 (Desktop — not the Server edition)

Instructions for the server edition are here.

Since Mac OS X doesn't have the "Server Admin" application, you'll need to start & configure MySQL manually from the command line.

Alternatively, if you are installing for a development environment only, you can use another instance of MySQL, such as those bundled with MAMP, XAMPP, the Acquia Drupal Stack Installer and other pre-compiled and packaged server stacks. To do this;

  1. Skip the steps about:
    1. passenger-install-apache2-module
    • Use webrick instead
    • You probably don't need gem install passenger or the Passenger preferences pane — but I'm not certain.
    2. Enabling MySql with Server Admin
    3. Establishing defaults with rake and RAILS_ENV
  2. You may need to run the following command instead of sudo gem install mysql — I'm not sure.
    sudo env ARCHFLAGS="-arch x86_64" gem install --no-rdoc --no-ri mysql -- --with-mysql-config=/usr/local/bin/mysql_config
  3. You'll still need to download and install MySql binaries from the opensource.apple.com link in RedmineInstallOSXServer. gem needs this in order to build the ruby-to-mysql plugin.
  4. Start your server-stack and check the MySQL server is running
  5. Either;
    1. Use the stack's phpMyAdmin or it's equivalent tool to create the database and user, OR
    2. Check that mysql on the command line points to the mysql binary for your stack (which mysql) and create a database and user as per RedmineInstallOSXServer.
  6. Link Mac OS X's socket to the stack's socket to trick Ruby into finding the right mysql instance:
    sudo ln -s /Applications/acquia-drupal/mysql/data/mysql.sock /var/mysql/mysql.sock
  7. Start the Ruby web server with ruby script/server webrick -e production.
    If you set the development database settings in config/databases.yaml instead of the production database settings, you can replace production with development in the above command.
  8. Point your web browser at http://localhost:3000

Updated by Bevan Rudge over 14 years ago · 2 revisions