Pre Requirements

IRCAnywhere requires a few tools to be installed before we can start installing the package. The following tools are required to proceed if you have these installed you can skip to the next page;

  • nodejs
  • npm
  • MongoDB

Installing Node.js and Npm

First we’ll install nodejs and npm we recommend latest stable versions as always.

  • Fedora
$ sudo yum install nodejs npm -y
  • Mac OSX
$ brew install node npm
  • Debian/Ubuntu

Latest versions of nodejs include npm aswell.

$ sudo add-apt-repository ppa:chris-lea/node.js
$ apt-get update
$ apt-get install nodejs

If this is not working for any reason, usually something similar to:

Err wheezy/main Sources
404  Not Found

Then I would recommend installing node with nvm

$ curl | sh
$ nvm install 0.10
$ nvm use 0.10
$ nvm alias default 0.10

Installing With The Installer

In the latest development branch we now have an install script to automate everything past this point. If you’re running in a production environment it’s recommended to install your own global version of MongoDB so if the time comes you’re ready to scale it and secure it. Although if you’re just interested in a quick get up and go then it’s worth skipping to this section.

Installing MongoDB

Next we’ll install MongoDB and set it up correctly.

  • Fedora

$ yum install mongo-10gen mongo-10gen-server

You may need to create a /etc/yum.repos.d/mongodb.repo file and add the following to it.

64-bit operating system.

name=MongoDB Repository

32-bit operating system (not recommended for production).

name=MongoDB Repository
  • Mac OSX

    $ brew update
    $ brew install mongodb
  • Debian/Ubuntu

    $sudo apt-key adv --keyserver hkp:// --recv 7F0CEB10
    $echo 'deb dist 10gen' | sudo tee /etc/apt/sources.list.d/mongodb.list
    $sudo apt-get update
    $sudo apt-get install mongodb-org

The next step is setting up MongoDB correctly so we can take advantage of the oplog tailing features, to do this we need to start MongoDB with a replica set. It’s likely your package manager started MongoDB when they finished installing it, so we need to shut it down first, do this with the following commands.

$ mongo
> use admin;
> db.shutdownServer();


$ killall -12 mongod

We now need to start mongodb with a single replica set for oplog tailing. Although a single mongo server wouldn’t need to be a replica set usually, they allow it for testing purposes, if you’re planning on running ircanywhere in a production environment with a good number of users I would recommend setting up an actual cluster of servers here (you’ll hear more about clustering ircanywhere processes together soon).

If you are running MongoDB from a config file, which is usually located at /etc/mongodb.conf. Then you can edit this file and include the following line at the bottom:

replSet = rs0
fork = true

You can then restart MongoDB using the config file with the following commands:

$ mongod --config /etc/mongodb.conf
$ mongo
> rs.initiate()

If the file doesn’t exist you can start MongoDB with the following options to initiate a replica set (although I would recommend having a config file to save you passing in these options every time you reboot. Although this is getting out of the scope of this guide). You may need to run it as sudo.

$ mongod --logpath /var/log/mongodb.log --replSet rs0
$ mongo

Once you’ve started the mongo instance sucessfully you can connect to it with the mongo command, once connected you should see this:

MongoDB shell version: 2.4.9
connecting to: test

If you see the :PRIMARY> suffix then you’ve set the replica set up successfully. If you’re still having trouble you can try following this more detailed guide at