Creating a Review Board Site¶

1. Create the Database¶

Before you create the Review Board site, you’ll need to create a database. The particular steps for this depend on the database server software that you intend to use.

[client]
default-character-set=utf8mb4

[mysqld]
character-set-server=utf8mb4

$ mysql -u <username> -p -h <hostname>
mysql> CREATE DATABASE <database_name>;
mysql> CREATE USER '<rb_user>' IDENTIFIED BY '<rb_password>';
mysql> GRANT ALL PRIVILEGES ON <database_name>.* to '<rb_user>';

$ mysql -u root -p -h db.example.com
mysql> CREATE DATABASE reviewboard;
mysql> CREATE USER 'rbuser'@'%' IDENTIFIED BY 's3cr3t';
mysql> GRANT ALL PRIVILEGES ON reviewboard.* to 'rbuser'@'%';

$ psql -U <username> -h <hostname>
postgres=# CREATE USER <rb_user> WITH PASSWORD '<rb_password>';
postgres=# CREATE DATABASE <database_name> WITH OWNER <rb_user>;

$ psql -U postgres -h db.example.com
postgres=# CREATE USER rbuser WITH PASSWORD 's3cr3t';
postgres=# CREATE DATABASE reviewboard WITH OWNER rbuser;

2. Create the Site Directory¶

1. Begin installation by running the following command:

   Python Virtual EnvironmentsSystem Installs

   $ /opt/reviewboard/bin/rb-site install <path>
   

   For example:

   $ /opt/reviewboard/bin/rb-site install /var/www/reviews.example.com
   

2. Answer the questions about your install. These will include: including:

   • The domain name for the server

   • The path for the server, relative to the domain

   • The database information (as configured above)

   • The memcached server address

   • The username and password to use for the Review Board administrator account

3. Once finished, follow rb-site’s instructions to complete your installation.

   We’ll go over those next.

3. Configure Permissions¶

Review Board must have write access to the following directories and their subdirectories:

• sitedir/data

• sitedir/htdocs/media/uploaded

• sitedir/htdocs/media/ext

• sitedir/htdocs/static/ext

Since Review Board is run by your web server, these must be writable by the web server’s user. If using Apache, this will likely be www-data or apache2. Please check the user your web server is running as for details.

For example:

$ cd /var/www/reviews.example.com
$ chown -R www-data data
$ chown -R www-data htdocs/media/uploaded
$ chown -R www-data htdocs/media/ext
$ chown -R www-data htdocs/static/ext

4. Configuring SELinux (optional)¶

Your system may be configured for SELinux, which is designed to keep your Linux distribution secure. This is usually enabled by default on Red Hat Enterprise, Fedora, and CentOS Stream.

If enabled, you will need to configure additional permissions:

1. Check if SELinux is enabled:

   $ getenforce
   Enforcing
   

   If this says “Enforcing”, SELinux is currently enabled, and you’ll need to continue on with the next step.

   If this says “Permissive” or “Disabled”, then SELinux is not enabled. If you don’t plan to enable SELinux, you can skip this section.

2. Grant your web server access to the necessary services:

   $ setsebool -P httpd_can_connect_ldap 1
   $ setsebool -P httpd_can_network_connect 1
   $ setsebool -P httpd_can_network_connect_db 1
   $ setsebool -P httpd_can_network_memcache 1
   $ setsebool -P httpd_can_sendmail 1
   $ setsebool -P httpd_unified 1
   

3. Register permissions on your Review Board site directory.

   This tells SELinux what policies to set when applying permissions. They’ll be applied in the next step.

   We’ll use /var/www/reviews.example.com for this example:

   $ semanage fcontext -a -t httpd_sys_content_t \
         "/var/www/reviews.example.com/(conf|htdocs)(/.*)?"
   $ semanage fcontext -a -t httpd_sys_rw_content_t \
         "/var/www/reviews.example.com/(data|tmp|htdocs/static/ext)(/.*)?"
   $ semanage fcontext -a -t httpd_sys_rw_content_t \
         "/var/www/reviews.example.com/htdocs/media/(ext|uploaded)(/.*)?"
   $ semanage fcontext -a -t httpd_log_t \
         "/var/www/reviews.example.com/logs(/.*)?"
   

4. Apply the new policies to your site directory.

   $ restorecon -Rv /var/www/reviews.example.com
   

   Important

   You may need to re-run this when upgrading your site directory.

If you need any help with SELinux, reach out to us for support.

5. Configure the Web Server¶

Your web server must be configured to serve Review Board. This section will go over different configurations that are available.

Review Board is known to work well with the following configurations:

• Apache + mod_wsgi (the most common configuration)

• Nginx + Gunicorn

• Nginx + uWSGI

$ apt-get install apache2 libapache2-mod-wsgi-py3

$ yum install httpd mod_wsgi

$ cd /etc/apache2
$ cp /var/www/reviews.example.com/conf/webconfs/apache-wsgi.conf \
     sites-available/reviews.example.com.conf
$ ln -s sites-available/reviews.example.com.conf \
        sites-enabled/

$ cd /etc/httpd/conf.d
$ cp /var/www/reviews.example.com/conf/webconfs/apache-wsgi.conf \
     reviews.example.com.conf

<VirtualHost *:80>
  # NOTE: If you change the ServerName or add ServerAlias, you must change
  #       ALLOWED_HOSTS to match. This can be found in:
  #
  #       /var/www/reviews.example.com/conf/settings_local.py
  ServerName reviews.example.com


  # Enable HTTP/2 support, if available.
  Protocols h2 h2c http/1.1


  # If enabling SSL on Apache, uncomment these lines and specify the
  # SSL paths.
  #
  # You may also need to add additional options, depending on your setup.
  # Please refer to the Apache documentation.
  #
  # SSLEngine On
  # SSLCertificateFile /var/www/reviews.example.com/conf/ssl/fullchain.pem
  # SSLCertificateKeyFile /var/www/reviews.example.com/conf/ssl/privkey.pem


  # mod_wsgi Embedded Mode configuration
  #
  # This default configuration enables Embedded Mode, but you can remove
  # this and uncomment Daemon Mode below.
  #
  # Embedded mode is simpler to configure, but daemon mode is recommended
  # in production environments.
  WSGIPassAuthorization On
  WSGIScriptAlias "/" "/var/www/reviews.example.com/htdocs/reviewboard.wsgi/"


  # mod_wsgi Daemon Mode configuration
  #
  # Uncomment this to use daemon mode.
  #
  # Make sure to choose a suitable number of processes and threads for your
  # server.
  #
  # WSGIPassAuthorization On
  # WSGIProcessGroup reviews_example_com
  # WSGIDaemonProcess \
  #     reviews_example_com \
  #     display-name=%{GROUP} \
  #     processes=6 threads=30
  # WSGIScriptAlias \
  #     "/" \
  #     "/var/www/reviews.example.com/htdocs/reviewboard.wsgi" \
  #     process-group=reviews_example_com application-group=%{GROUP}
  # WSGIImportScript \
  #     /var/www/reviews.example.com/htdocs/reviewboard.wsgi \
  #     process-group=reviews_example_com application-group=%{GROUP}


  # Log configuration
  #
  # NOTE: We recommend adding these to your logrotate configuration.
  ErrorLog /var/www/reviews.example.com/logs/error_log
  CustomLog /var/www/reviews.example.com/logs/access_log combined


  # Aliases for serving static files.
  DocumentRoot "/var/www/reviews.example.com/htdocs"
  ErrorDocument 500 /errordocs/500.html
  Alias /media "/var/www/reviews.example.com/htdocs/media"
  Alias /static "/var/www/reviews.example.com/htdocs/static"
  Alias /errordocs "/var/www/reviews.example.com/htdocs/errordocs"
  Alias /robots.txt "/var/www/reviews.example.com/htdocs/robots.txt"

  <Directory "/var/www/reviews.example.com/htdocs">
    AllowOverride All
    Options -Indexes +FollowSymLinks

    <IfVersion < 2.4>
      Allow from all
    </IfVersion>

    <IfVersion >= 2.4>
      Require all granted
    </IfVersion>
  </Directory>

  # Prevent the server from processing or allowing the rendering of
  # certain file types.
  <LocationMatch ^(/(static|media|errordocs))>
    SetHandler None
    Options None

    AddType text/plain .html .htm .shtml .php .php3 .php4 .php5 .phps .asp
    AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht .jsp .sh .rb

    <IfModule mod_php5.c>
      php_flag engine off
    </IfModule>
  </LocationMatch>

  <Location "/media/uploaded">
    # Force all uploaded media files to download.
    <IfModule mod_headers.c>
      Header set Content-Disposition "attachment"
    </IfModule>
  </Location>
</VirtualHost>

$ gunicorn \
      --bind=0.0.0.0:8000 \
      --log-level=info \
      --timeout=120 \
      --workers=6 \
      --threads=30 \
      --log-file=/var/www/reviews.example.com/logs/gunicorn.log \
      --env REVIEWBOARD_SITEDIR=/var/www/reviews.example.com \
      reviewboard.wsgi

# This is a sample configuration file for a Nginx -> Gunicorn deployment for
# Review Board.
#
# Please go through this file and make sure it's suitable for your setup
# before using it.

server {
  # NOTE: If you change the server_name, you must change ALLOWED_HOSTS to
  #     match. This can be found in:
  #
  #     /var/www/reviews.example.com/conf/settings_local.py
  server_name reviews.example.com;

  # If enabling SSL on Nginx, remove the "listen 80" lines below and use
  # configure these settings instead. You will also need to change
  # X-Forwarded-Ssl below.
  #
  # listen [::]:443 ssl http2;
  # listen 443 ssl http2;
  # ssl_certificate /var/www/reviews.example.com/conf/ssl/fullchain.pem;
  # ssl_certificate_key /var/www/reviews.example.com/conf/ssl/privkey.pem;
  listen [::]:80;
  listen 80;

  # Log configuration
  #
  # NOTE: We recommend adding these to your logrotate configuration.
  access_log /var/www/reviews.example.com/logs/nginx_access_log;
  error_log /var/www/reviews.example.com/logs/nginx_error_log;

  location / {
    proxy_pass http://127.0.0.1:8000;
    proxy_redirect        off;

    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_set_header X-Forwarded-Proto $scheme;

    # NOTE: Set this to "on" if using SSL.
    proxy_set_header X-Forwarded-Ssl off;

    client_max_body_size        10m;
    client_body_buffer_size     128k;
    proxy_connect_timeout       90;
    proxy_send_timeout          90;
    proxy_read_timeout          90;
    proxy_headers_hash_max_size 512;
    proxy_buffer_size           4k;
    proxy_buffers               4 32k;
    proxy_busy_buffers_size     64k;
    proxy_temp_file_write_size  64k;
  }

  location /media/ {
    alias /var/www/reviews.example.com/htdocs/media/;
    expires max;
    add_header Cache-Control public;
  }

  location /static/ {
    alias /var/www/reviews.example.com/htdocs/static/;
    expires max;
    add_header Cache-Control public;
  }

  location /errordocs/ {
    alias /var/www/reviews.example.com/htdocs/errordocs/;
    expires 5d;
  }

  location /robots.txt {
    alias /var/www/reviews.example.com/htdocs/robots.txt;
    expires 5d;
  }
}

$ uwsgi /var/www/reviews.example.com/conf/webconfs/uwsgi.ini

[uwsgi]
module = reviewboard.wsgi:application
env=REVIEWBOARD_SITEDIR=/var/www/reviews.example.com

master = true
processes = 6
threads = 30

socket = /var/www/reviews.example.com/data/uwsgi.sock
cmod-socket = 664
vacuum = true

die-on-term = true

# This is a sample configuration file for a Nginx -> uWSGI deployment for
# Review Board.
#
# Please go through this file and make sure it's suitable for your setup
# before using it.

server {
  # NOTE: If you change the server_name, you must change ALLOWED_HOSTS to
  #     match. This can be found in:
  #
  #     /var/www/reviews.example.com/conf/settings_local.py
  server_name reviews.example.com;

  # If enabling SSL on Nginx, remove the "listen 80" lines below and use
  # configure these settings instead:
  #
  # listen [::]:443 ssl http2;
  # listen 443 ssl http2;
  # ssl_certificate /var/www/reviews.example.com/conf/ssl/fullchain.pem;
  # ssl_certificate_key /var/www/reviews.example.com/conf/ssl/privkey.pem;
  listen [::]:80;
  listen 80;

  # Log configuration
  #
  # NOTE: We recommend adding these to your logrotate configuration.
  access_log /var/www/reviews.example.com/logs/nginx_access_log;
  error_log /var/www/reviews.example.com/logs/nginx_error_log;

  location / {
    include uwsgi_params;
    uwsgi_pass unix:/var/www/reviews.example.com/data/uwsgi.sock;
  }

  location /media/ {
    alias /var/www/reviews.example.com/htdocs/media/;
    expires max;
    add_header Cache-Control public;
  }

  location /static/ {
    alias /var/www/reviews.example.com/htdocs/static/;
    expires max;
    add_header Cache-Control public;
  }

  location /errordocs/ {
    alias /var/www/reviews.example.com/htdocs/errordocs/;
    expires 5d;
  }

  location /robots.txt {
    alias /var/www/reviews.example.com/htdocs/robots.txt;
    expires 5d;
  }
}

6. Configure Task Scheduling¶

Cron is used for automatically running periodic maintenance tasks, including:

• Updating the search index

• Clearing expired login sessions

Your site directory contains a sample Crontab file at sitedir/conf/cron.conf. You can customize this and then register it with Cron as the web server:

$ sudo -u <web_server_user> crontab /path/to/sitedir/conf/cron.conf

For example:

$ sudo -u apache2 crontab /var/www/reviews.example.com/conf/cron.conf

A sample Crontab configuration looks like:

# Update search index every 10 minutes
0,10,20,30,40,50 * * * * "/opt/reviewboard/bin/rb-site" \
    manage "/var/www/reviews.example.com" update_index -- -a 1

# Clear expired sessions once a day at 2am
0 2 * * * "/opt/reviewboard/bin/rb-site" \
    manage "/var/www/reviews.example.com" clearsessions

# Update search index every 10 minutes
0,10,20,30,40,50 * * * * "/usr/bin/python3.11" "/usr/bin/rb-site" \
    manage "/var/www/reviews.example.com" update_index -- -a 1

# Clear expired sessions once a day at 2am
0 2 * * * "/usr/bin/python3.11" "/usr/bin/rb-site" \
    manage "/var/www/reviews.example.com" clearsessions

You’re Done!¶

Now that Review Board is installed and your site directory is created, you can start your web server and navigate to Review Board.

You’ll want to configure Review Board and connect it to any source code management systems you’re using.

To learn more:

• Configuring Review Board

• Managing Repositories

• Administration Guide