Installing IdeaLoom


  • On Mac OS X 10.9.2: The system python is incompatible with the clang 5.1. You need to remove all occurences of -mno-fused-madd in /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ Also renew (or delete) the corresponding .pyc, .pyo files.
  • For production on linux using nginx/uwsgi you need the following ppa - Necessary for both saucy 13.10, raring 13.04, trusty 14.04 - Not needed for vivid 15.04 and later
apt-add-repository ppa:chris-lea/uwsgi
apt-get install nginx uwsgi uwsgi-plugin-python3

Setup a development environment

Install fabric and a SSH server

You need fabric 1.5.1 and a SSH server installed. Fab should be able to ssh into the target server, even if it’s localhost. Fab will repeatedly ask for the login password, unless you set up ssh-agent on your host and ~/.ssh/authorized_keys on the target server.

Here is how to install the ssh server on Mac and on Ubuntu.

On Mac

First install Homebrew by following the instructions at ; or simply paste the following in the terminal:

ruby -e "$(curl -fsSL"

Make sure /usr/local/bin is in your $PATH. Then, install the homebrew python and fabric:

brew install python fabric

MacOS has a SSH server installed. To activate it, go to System Preferences in the Apple Menu, then to the Sharing tab. Ensure the “Remote login” checkbox is active.

On Ubuntu

You can get all that you need to bootstrap with:

apt-get install fabric git openssh-server sudo

Check out the code repository, install build dependencies, and bootstrap

You can run either:

fab install_single_server
fab bootstrap:projectpath=~/idealoom
cd ~/idealoom


git clone
cd idealoom
fab -c configs/develop.rc install_single_server
fab -c configs/develop.rc bootstrap_from_checkout

Note: If on Mac, command fab -c configs/develop.rc install_single_server outputs “Low level socket error: connecting to host localhost on port 22: Unable to connect to port 22 on”, you have to go to System preferences > Sharing > check “Enable remote login”, and retry the command.

Note: If you get the following error: fabric.exceptions.NetworkError: Incompatible ssh server (no acceptable macs) Then you’ll need to reconfigure your ssh server


Note: memcached and redis must be running already.

cd ~/idealoom

Only the first time you run it:

source venv/bin/activate
circusd circusd.conf

Creating a user the first time you run IdeaLoom (so you have a superuser):

assembl-add-user --email --name "Your Name" --username desiredusername --password yourpassword local.ini

Note: Just running $venv/bin/circusd will NOT work, as celery will run command line tools, thus breaking out of the environment. You need to run source venv/bin/activate from the same terminal before running the above

Note: If you do not want to source activate every time, you can hook it in your shell using something like Autoenv. Another option is to use VirtualenvWrapper and its Helper. At least one of us uses VirtualFish with auto-activation.

On subsequent runs, just make sure circusd is running.

Then, start the development server and compass with this command:

env CIRCUSCTL_ENDPOINT=ipc://`pwd`/var/run/circus_endpoint circusctl start pserve

You can now type http://localhost:6543 in your browser and log in using the credentials you created.

Multiple environments

If you want to run multiple environments on your machine, you should have different values for various parameters in .rc files in the configs directory. You would create a configs/local.rc based on configs/develop.rc, as described in IdeaLoom Configuration files.

Once you create your local.rc, re-run the fab -c configs/local.rc app_setup step.

The variables that have to be different between instances are the following (for convenience they are marked with UNIQUE_PER_SERVER in the ini file):

public_port = 6543
changes.socket = ipc:///tmp/assembl_changes/0
changes.websocket.port = 8085
redis_socket = 0
webpack_port = 8080
server:main__port = 6543

Most of these are ports, and it should be easy to find an unoccupied port; in the case of changes.socket, you simply need a different filename, and in the case of celery_task.*.broker, the final number has to be changed to another low integer.

A note on vagrant

If you use vagrant, we have a few processes that expect to use socket files in %(here)s. Vagrant does not allow creating sockets in a shared folder; so if you insist on using vagrant, make sure to move sockets locations. Some are defined in circusd.conf.tmpl, and changes.socket is defined in the .ini files.

Updating an environment

cd ~/idealoom
#Any git operations (ex:  git pull)
fab -c configs/develop.rc app_compile
$venv/bin/circusctl start pserve webpack

You can monitor any of the processes, for example pserve, with these commands:

tail -f var/log/pserve.log
tail -f var/log/pserve.err.log

In production:

#(Instead of dev:*. You may have to stop dev:*)
$venv/bin/circusctl start uwsgi

Updating an environment after switching branch locally (will regenerate css, all compiled files, update dependencies, database schema, etc.):

fab -c configs/develop.rc app_compile

Updating an environment to it’s specified branch, tag or revision:

cd ~/idealoom
fab -c configs/develop.rc app_fullupdate

Schema migrations

Upgrade to latest manally:

alembic -c local.ini upgrade head

Create a new one:

alembic -c local.ini revision -m "Your message"
Make sure to verify the generated code...

Autogeneration (–autogenerate) isn’t supported since we don’t have full reflexion support in virtuoso’s sqlalchemy driver.

Ontology Submodule

The ontology module is a git submodule. As a result, after pulling in changes, update with the following:

git submodule update --init

Setting up a production dedicated instance

In what follows, we will assume that the nginx web server runs in group www-data, and that the idealoom server runs under a dedicated user, called idealoom_user, which should not be a sudoer. We suggest defining a group (idealoom_group) for all idealoom users. Note: For a simple single-server setup, it is also possible to use the www-data user directly, and to put idealoom in /var/www.

Start as a user with sudo access

sudo apt-get install fabric git openssh-server
sudo apt-get install nginx uwsgi uwsgi-plugin-python3
sudo addgroup idealoom_group
sudo adduser idealoom_user
sudo usermod -G www-data -G idealoom_group idealoom_user

By default, postgres will not use passwords from postgres users who connect through the Unix socket domain (versus a network connection). So if you want to make your database to be safer and ask for password anyway, edit your /etc/postgresql/9.1/main/pg_hba.conf file and

# replace
local   all             all                                peer
# by
local   all             all                                md5

and then run

sudo service postgresql restart

Then, as the idealoom_user:

sudo -u idealoom_user -i

git clone
cd idealoom

Change the values for:

If you use sentry to monitor:

  • pipeline
  • raven_url
  • dsn

Also set up the raven_url and raven client key where appropriate.

Put your chosen database username and password in

  • db_database
  • db_user
  • db_pasasword
  • sqlalchemy.url # CAREFUL: sqlalchemy.url needs to be edited TWICE in the file
  • assembl.admin_email

Just type a random strings in these two: session.secret, security.email_token_salt

Make sure your ssl works, and set

accept_secure_connection = true
require_secure_connection = true

Otherwise, your are jeopardiszing passwords…

The following must all be unique to the instance. If you only have one instance on the server, you can keep the defaults

  • changes.socket
  • changes.websocket.port
  • public_port

The public_port field (located in app:assembl section) is the actual port used by the UWSGI server which is rerouted through the reverse proxy served by nginx. For production context, use 80. There is also a port field in server:main section, which defaults to 6543. If not proxied by nginx or something, port needs to match public_port.

Also, set the uid field of your ini file to the username of the unix user you created above. For example: uid = idealoom_user If you have not added this user to the www-data group as advised previously (or to a group which is common with the ngnix user), then you also have to set the gid field to a common group name.

If you do not have an SSL certificate, then you have to set accept_secure_connection = false and require_secure_connection = false (because if you set accept_secure_connection = true, then the login page on IdeaLoom will try to show using https, which will not work).

(exit to sudoer account)

exit  # this logs out from the idealoom_user user, back to the initial sudoer account
cd /home/idealoom_user/idealoom
fab -c configs/develop.rc install_single_server
sudo -u idealoom_user -i  # back to the idealoom user
cd /home/idealoom_user/idealoom
fab -c configs/develop.rc bootstrap_from_checkout
source venv/bin/activate
assembl-add-user --email --name "Your Name" --username desiredusername --password yourpassword local.ini

Copy the content of doc/sample_nginx_config/ into a new nginx config file, at /etc/nginx/sites-available/{{}} (and replace its filename by your own domain):

cp doc/sample_nginx_config/ /etc/nginx/sites-available/{{}}

Edit this file using your favorite editor to match your domain and architecture (including SSL settings if any). Activate this site, using:

cd /etc/nginx/sites-enabled/
ln -s /etc/nginx/sites-available/{{}} .

Test that your configuration file works, by running:

/usr/sbin/nginx -t

Restart nginx:

/etc/init.d/nginx restart

Copy the content of doc/sample_systemd_script/idealoom.service into /etc/systemd/system/idealoom.service, and modify fields IDEALOOM_PATH, User and Description.

systemctl enable idealoom
service idealoom restart

There is more to setup: You may set up an external or internal SMTP server (TODO), an external IMAP server (TODO), and Piwik

The Setting up Dovecot and VMM document explains how to set up an internal IMAP server.