Installing Redis on Mac OSX

Get source and install

$ wget 
$ tar xzf redis-2.2.12.tar.gz 
$ cd redis-2.2.12 
$ make
$ make install 

And it should be up and running on:


For Redis server to start on boot

$ sudo nano /Library/LaunchDaemons/org.redis.redis-server.plist

Copy the  following to the the file you just created.

Create the log dir if it doesn’t exists yet

sudo mkdir /var/log/redis

Load and launch the Daemon:

sudo launchctl load /Library/LaunchDaemons/org.redis.redis-server.plist
sudo launchctl start org.redis.redis-server

Hope it helps ;)

16 thoughts on “Installing Redis on Mac OSX

    • Very true Félix, but compiling it myself, set it to start on boot, etc… is helping me understanding how osx works. Both are valid ways to do it :)

      Thanks for the comment :)

  1. Excellent, thank you!, just wanted to mention: the last line “sudo launchctl start org.redis.redis-server.plist” didn’t work for me, but “sudo launchctl start org.redis.redis-server” did (without “.plist”). :)

    • Hi,

      I’m not sure I’m following you. You want to install it but only start it “on demand”? If this is true, just don’t do anything else after, make install.

      To manually start the server just execute

  2. brew update
    brew doctor (just in case)
    brew info redis
    MacBook-Pro-Roman:redis-2.8.17 retgoat$ brew info redis
    redis: stable 2.8.17 (bottled), HEAD
    /usr/local/Cellar/redis/2.8.17 (10 files, 1,4M) *
    Poured from bottle
    ==> Caveats
    To reload redis after an upgrade:
    launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.redis.plist
    launchctl load ~/Library/LaunchAgents/homebrew.mxcl.redis.plist
    Or, if you don’t want/need launchctl, you can just run:
    redis-server /usr/local/etc/redis.conf

    brew install redis

    Mac OS X Mavericks

  3. Works nicely. I’ve added a script (a total ripoff of apachectl):




    if [ “x$ARGV” = “x” ] ; then

    case $ARGV in
    # echo “Starting Redis Server…”
    # echo “Stopping Redis Server…”
    # echo “Restarting Redis Server…”
    $LAUNCHCTL unload -w $LAUNCHD_JOB 2> /dev/null
    # echo “unknown command”

    exit $ERROR

    (I’m happy that there are still people who do their own builds instead of using homebrew and macports. I’ve used such things for the last time after it messed up my system so I had to re-install from scratch. It took me more than 6 months to get my system configured *almost* as it was; so I prefer bulding manually so I know more or less what’s going on).

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s