Ubuntu Linux Server¶
However, you may prefer to run oTree on a proper Linux server. Reasons may include:
Your lab doesn’t have internet
You want full control over server configuration
You want better performance (local servers have less latency)
If you are experienced in Django server setup, you just need to know that setting up an oTree server is the same as any Django project, except:
You need Redis
You start the server with
otree prodserver, rather than a WSGI server.
Install apt-get packages¶
sudo apt-get install python3-pip python3-dev libpq-dev postgresql postgresql-contrib redis-server git
Create a virtualenv¶
It’s a best practice to use a virtualenv:
python3 -m venv venv_otree
To activate this venv every time you start your shell, put this in your
Once your virtualenv is active, you will see
(venv_otree) at the beginning
of your prompt.
oTree’s default database is SQLite, which is fine for local development, but insufficient for production. We recommend you use PostgreSQL.
Change users to the
postgres user, so that you can execute some commands:
sudo su - postgres
Then start the Postgres shell:
Once you’re in the shell, create a database and user:
CREATE DATABASE django_db; alter user postgres password 'password';
Exit the SQL prompt:
Return to your regular command prompt:
Then add this line to the end of your .bashrc/.profile:
DATABASE_URL is defined, oTree will use it instead of the default SQLite.
When you run
otree resetdb later,
if you get an error that says “password authentication failed for user”,
hba_auth.conf file, and on the lines for
md5 (or whatever it currently is) to
If you installed
apt-get as instructed earlier,
Redis should be running on port 6379. You can test with
which should output
If there was an installation problem, you can try installing Redis from an alternate source, e.g. here.
Push your code to the server¶
You can get your code on the server using SCP, SFTP, Git, etc.
For this tutorial, we will assume you are storing your files under
Reset the database on the server¶
On the server,
cd to the folder containing your oTree project.
Install the requirements and reset the database:
pip3 install -r requirements.txt otree resetdb
Running the server¶
If you are just testing your app locally, you can use the usual
However, when you want to use oTree in production, you need to run the production server, which can handle more traffic.
Note: oTree does not run with typical Django WSGI servers like
because it is ASGI based.
Testing the production server¶
From your project folder, run:
otree prodserver 8000
Then navigate in your browser to your server’s
IP/hostname followed by
If you’re not using a reverse proxy like Nginx or Apache,
you probably want to run oTree directly on port 80.
This requires superuser permission, so let’s use sudo,
but add some extra args to preserve environment variables like
sudo -E env "PATH=$PATH" otree prodserver 80
Try again to open your browser; this time, you don’t need to append :80 to the URL, because that is the default HTTP port.
prodserverdoes not restart automatically when your files are changed.
prodserverautomatically runs Django’s
collectstaticto collect your files under
_static_root/. If you have already run
collectstatic, you can skip it with
Set remaining environment variables¶
Add these in the same place where you set
export OTREE_ADMIN_PASSWORD=my_password #export OTREE_PRODUCTION=1 # uncomment this line to enable production mode export OTREE_AUTH_LEVEL=DEMO
(Optional) Process control system¶
Once the server is working as described above, it’s a good practice to use a process control system like Supervisord or Circus. This will restart your processes in case they crash, keep it running if you log out, etc.
Install Circus, then create a
circus.ini in your project folder,
with the following content:
[watcher:webapp] cmd = otree args = prodserver 80 use_sockets = True copy_env = True
sudo -E env "PATH=$PATH" circusd circus.ini
If this is working properly, you can start it as a daemon:
sudo -E env "PATH=$PATH" circusd --daemon circus.ini --log-output=circus-logs.txt
To stop circus, run:
(Optional) Apache, Nginx, etc.¶
You cannot use Apache or Nginx as your primary web server, because oTree must be run with an ASGI server. However, you still might want to use Apache/Nginx as a reverse proxy, for the following reasons:
You are trying to optimize serving of static files (though oTree uses Whitenoise, which is already fairly efficient)
You need to host other websites on the same server
You need features like SSL or proxy buffering
If you set up a reverse proxy, make sure to enable not only HTTP traffic but also websockets. no Troubleshooting —————
If you get strange behavior, such as random changes each time the page reloads, it might be caused by another oTree instance that didn’t shut down. Try stopping oTree and reload again. Also make sure that you are not sharing the same Postgres or Redis databases between two oTree instances.