This guide shows how to install and configure brep on a "deployment" machine as opposed to a "development" one (see INSTALL-DEV for the latter). Here we assume you are using a systemd-based distribution. If not, then you will need to replace systemctl commands with the equivalend init.d ones. 1. Create 'brep' User This user will be used to run the brep repository loader. We will also use its home directory to build and install the brep module, store its configuration, etc. We create this user with a disabled password so only root will be able to operate as brep. Because of this restriction we will allow brep to run sudo without a password: # adduser --disabled-password brep # echo "brep ALL=(ALL) NOPASSWD:ALL" >/etc/sudoers.d/brep # chmod 0440 /etc/sudoers.d/brep In the rest of this guide commands that start with the $ shell prompt are expected to be executed as the brep user and in its home directory. 2. Install Prerequisites a) Install a C++ compiler using your distribution's package. b) Install PostgreSQL 9.x and Apache2 using your distribution's packages. Also check that the files in /home/brep are readable by "others". If they are not, then run the following command to grant Apache2 read access: $ setfacl -dm g:www-data:rx /home/brep In the above command and in the rest of this guide replace www-data with the user name under which Apache2 is running (See the "User" directive in the Apache2 .conf file). [Note that strictly speaking www-data in the above command is the Apache2 group, not user. However, most installations use the same name for both.] c) Install PostgreSQL and Apache2 development files. Specifically, we need PostgreSQL's libpq and Apache's libapr and web server development files. Below are the names of their packages for some distributions: Debian/Ubuntu: libpq-dev libapr1-dev apache2-dev Fedora/RHEL: posqtgresql-devel apr-devel httpd-devel FreeBSD: postgresql94-client apr apache24 d) Install build2-toolchain by following its INSTALL file instructions. You can build build2-toolchain using brep's login and in its home directory. e) Install libodb-pgsql and libstudxml [Currently we use pre-release versions of these libraries so they have to be built from source.] Download source packages for the two libraries from the same location as build2-toolchain. Then unpack, build, and install: $ cd libXXX-X.Y.Z $ ./configure CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib \ --prefix=/usr/local $ make $ sudo make install Again, you can use brep's login/home directory for this. See the INSTALL file for each library for more information. 3. Build and Install brep $ mkdir brep install $ cd brep In the following command line, replace and with directories that contain the apr.h and httpd.h headers, respectively. Below are their locations for some distributions: Debian/Ubuntu: /usr/include/apr-1.0 /usr/include/apache2 Fedora/RHEL: /usr/include/apr-1 /usr/include/httpd FreeBSD: /usr/local/include/apr-1 /usr/local/include/apache24 $ bpkg create \ cxx \ config.cxx.poptions="-I/usr/local/include -I -I" \ config.cxx.loptions=-L/usr/local/lib \ config.bin.rpath="/home/brep/install/lib /usr/local/lib" \ config.install.root=/home/brep/install $ bpkg add http://pkg.cppget.org/1/alpha $ bpkg fetch $ bpkg build brep $ bpkg install brep $ cd .. # Back to brep home. 4. Create PostgreSQL User and Database $ sudo sudo -u postgres psql # Note: double sudo is not a mistake. CREATE DATABASE brep; CREATE USER brep; GRANT ALL PRIVILEGES ON DATABASE brep TO brep; CREATE USER "www-data" INHERIT IN ROLE brep; Exit psql (^D), then make sure the logins work: $ psql $ sudo sudo -u www-data psql -d brep To troubleshoot, see PostgreSQL logs. 5. Create Database Schema and Load Repositories $ mkdir config $ edit config/brep-loader.conf # Loader configuration, see brep-loader(1). $ psql --quiet -f install/share/brep/package.sql $ install/bin/brep-loader config/brep-loader.conf To verify: $ psql -c 'SELECT name, summary FROM repository' 6. Setup Apache2 Module $ cp install/share/brep/etc/brep-module.conf config/ $ edit config/brep-module.conf # Adjust default values if required. If you happy to run with the default values, you can instead do: $ ln -s ../install/share/brep/etc/brep-module.conf config/ Here we assume you have setup an appropriate Apache2 virtual server. Open the corresponding Apache2 .conf file and add the following inside VirtualHost (you can also find this fragment in install/share/brep/etc/brep-apache2.conf): # Load the brep module. # LoadModule brep_module /home/brep/install/libexec/brep/mod_brep.so # Repository root. This is the part of the URL between the host name # and the start of the repository. For example, root value /pkg/ means # the repository URL is http://example.org/pkg/. Specify / to use the # web server root (e.g., http://example.org/). If using a different # repository root, don't forget to also change Alias directives below. # brep-root /pkg/ SetHandler brep DirectoryIndex disabled DirectorySlash Off # Brep module configuration. If you prefer, you can paste the contents # of this file here. However, you will need to prefix every option with # 'brep-'. # brep-conf /home/brep/config/brep-module.conf # Static brep content (CSS files). # Error "mod_alias is not enabled" # Note: trailing slashes are important! # Alias /pkg/@/ /home/brep/install/share/brep/www/ Require all granted # You can also serve the repository files from the repository root. # For example: # # http://example.org/pkg/1/... -> /path/to/repo/1/... # #AliasMatch ^/pkg/(\d+)/(.+) /path/to/repo/$1/$2 # # # Require all granted # Restart Apache2: $ sudo systemctl restart apache2 To verify, visit the repository root. To troubleshoot, see Apache logs. 7. Setup Periodic Loader Execution In this guide we will use the systemd user session to periodically run loader as the brep user. If your installation doesn't use systemd, then a cron job would be a natural alternative. As the first step, make sure systemd user sessions support is working for the brep user: $ systemctl --user status If there are any errors, make sure the dbus and libpam-systemd packages are installed, relogin as brep, and try again. If it still doesn't work, google for the error message and your distribution name. Next enable the brep's systemd session to remain running after logging off since we want the loader to run even when we are not logged in: $ sudo loginctl enable-linger brep $ mkdir -p .config/systemd/user $ cp install/share/brep/etc/systemd/brep-loader.* .config/systemd/user/ Start the service to make sure there are no issues: $ systemctl --user start brep-loader.service $ journalctl Start the timer and monitor it to make sure it fires: $ systemctl --user start brep-loader.timer $ journalctl -f If everything looks good, enable the timer to be started at boot time: $ systemctl --user enable brep-loader.timer 8. Upgrade Procedure During upgrade we will stop apache for what should normally be a short period of time. To ensure that there are no surprises, for production environments it is generally recommended to first perform the upgrade on a staging machine, for example, a VM with an identical setup. Save the previous installation and configuration, for example, using the brep version as a suffix: $ cp -r config config-`cat install/share/doc/brep/version` $ cp -r install install-`cat install/share/doc/brep/version` Build new version of brep: $ bpkg -d brep build brep Stop and disable loader: $ systemctl --user disable --now brep-loader.timer $ systemctl --user stop brep-loader.service Stop apache: $ sudo systemctl stop apache2 Install new brep: $ rm -rf install/* $ bpkg -d brep install brep Review brep-module.conf changes that may need to be merged: $ diff -u install/share/brep/etc/brep-module.conf config/brep-module.conf Update database schema: $ psql --quiet -f install/share/brep/package.sql Start and enable loader: $ systemctl --user start brep-loader.service $ systemctl --user status brep-loader.service If everything looks good, enable periodic execution: $ systemctl --user enable --now brep-loader.timer Start apache: $ sudo systemctl start apache2 To verify, visit the repository root. To troubleshoot, see Apache logs.