You have several options when choosing how to deploy bargate. You are strongly recommended to use the combination of uWSGI and nginx. bargate is a standard WSGI application so can be deployed via whatever method you like which supports WSGI applications.

nginx and uWSGI

This is the recommended option for deploying bargate, it offers the best performance and a range of options not available with other choices.

Install uWSGI and nginx

First we must install uWSGI and nginx. For uWSGI it is probably best to install this via ‘pip’ on any Linux platform so you get the latest version:

pip install uWSGI

If you can prefer you can install it via your distributions package manager.

For nginx you will need to use your package manager:

yum install nginx


apt-get install nginx

Configure uWSGI

uWSGI can be configured in multiple ways but you should probably use the ‘ini’ format. A sample configuration file for bargate is below:

socket = /var/run/uwsgi.sock
master = true
processes = 10
uid = nobody
gid = nobody
logto = /var/log/uwsgi.log
chmod-socket = 700
chown-socket = nginx
protocol = uwsgi
pidfile = /var/run/

If you’ve installed from git (rather than pip) you need to also add:

python-path = /opt/

And set the path (above /opt/) to the directory above where the git checkout is, i.e. if you checked out into /opt/bargate/ set the python-path to be /opt/.

You could place the uWSGI config file in /etc/bargate/uwsgi.ini or place it in whatever location suits your environment. All of the paths above can be changed, and the user should probably not be left as ‘nobody’ - pick a user or create a new one such as ‘bargate’.

The socket - the way uWSGI and nginx communicate - needs to be set so that nginx can communicate with it - and nothing else - so in the above example the socket is set to be owned by ‘nginx’ and permissions set to limit access to only the owner.

Whatever user/group you decide to set in the uid/gid options above must be able to read the config files for bargate. See Configuration for details about the bargate configuration file.

Next: You need to configure uWSGI to run as a service.

Run uWSGI as a service (systemd)

On systemd based platforms (e.g. RHEL7+, Debian 8+, Fedora 15+, Ubuntu 15.04+) you should create a service unit file. Create the file in /etc/systemd/system/bargate.service with the following contents:

Description=bargate web filestore server

ExecStart=/usr/bin/uwsgi /etc/bargate/uwsgi.ini --die-on-term


You should then ask systemd to reload:

systemctl daemon-reload

And then enable and start the service:

systemctl enable bargate
systemctl start bargate

Run uWSGI as a service (upstart)

On upstart based platforms (RHEL6, Ubuntu before 15.04, Fedora before 15) you should create /etc/init/bargate.conf with the following contents:

description "Bargate web filestore server"
start on runlevel [2345]
stop on runlevel [!2345]
exec /usr/bin/uwsgi /etc/bargate/uwsgi.ini --die-on-term

You can then simply start the service:

start bargate

The above example assumes you placed your uwsgi.ini file in /etc/bargate

Connect nginx to uWSGI

The final step is to configure nginx to speak to uWSGI. Configuring nginx itself is beyond the scope of this document, but you’ll need a ‘server’ block in your nginx configuration and within that add these lines to your nginx.conf:

client_max_body_size 257M;

location /static/
    root /opt/bargate/;

location / { try_files $uri @bargate; }
location @bargate
    include uwsgi_params;
    uwsgi_param HTTPS on;
    uwsgi_pass unix:/var/run/uwsgi.sock;

The above example assumes HTTPS - which you were going to use anyway, right?

You should set the ‘client_max_body_size’ option to be at least the same size as you tell Bargate to allow via the MAX_CONTENT_LENGTH configuration option.

If you intend on using search you may wish to add the ‘uwsgi_read_timeout’ and ‘uwsgi_send_timeout’ options. See Search for more information on how to set this up.

Enable and start nginx

You’ll want to enable and start nginx (on systemd systems):

systemctl enable nginx
systemctl start nginx

On Upstart based systems:

start nginx

On SysV systems (e.g. RHEL6):

chkconfig nginx on
service nginx start