Skip to content
Jonas Breder edited this page Jun 23, 2026 · 3 revisions

hroot uses MySQL as a database server. On many ubuntu versions, MySQL is already installed, you can install it with the following command:

sudo apt-get install mysql-server mysql-client libmysqlclient-dev

For more information see https://help.ubuntu.com/12.04/serverguide/mysql.html or the documentation of your linux distribution. You can also find a lot of information in the MySQL installation guide.

You should create a separate user for hroot with a secure password. In a production environment with real users, it is the best option to allow access only from the local machine (or the machine where the webserver is running). Since this is all basic server administration knowledge, we will not go into further detail here and assume that you have a database user named hroot and you can connect to the database server using this user with the command

mysql -u hroot -p

Depending on your setup, hroot will use the following databases:

  • If you want to develop or to test hroot locally, the database hroot_development will be used
  • If you want to run the automated test suite to verify your installation, the hroot_test database will be used
  • If you want to run hroot in a production environment (with real users and real data), typically a database named hroot_production is used

Of course you can use any other name, but it is useful to know the default names. If you use the standard configuration, these databases will be used and created.

HROOT - Hamburg Registration and Organization Online Tool

  1. Installation

    1. System Requirements and Prerequisites

    2. Docker (precompiled)

    3. Docker (self-compiled)

    4. Manual Deployment

    5. First steps after installation

    6. Environment Configuration

    7. Backup and Maintenance

    8. Starting a local server and running automated tests

    9. Basic configuration

    10. Language configuration and timezone

    11. Custom field definitions

  2. Updating an existing installation

  3. Overview

    1. Roles: Users, Admins, Experimenters, Banking‐Administrators
    2. Experiments, Sessions, session types
  4. Subject pool and user management

    1. Browsing the pool
    2. Exporting data
    3. Adding users
    4. Deleting users
    5. Finding duplicate users
    6. More user management
  5. Experiment management

    1. Managing Experiments
    2. Adding Sessions
    3. Experiment and Session Inheritance
    4. Reserving locations (booking)
    5. Assign participants from the pool
    6. Inviting participants
    7. Session management
    8. Waiting list
    9. Invitations Scheduling and Digests
  6. Admission

    1. QR Code Admission
    2. Online Waiting Room
    3. Online Surveys and Completion Links
  7. Calendar

  8. Sending messages

    1. Invitation emails
    2. Confirmation emails
    3. Session reminder emails
    4. Default locale and date formats
    5. SMS and Push Notifications
  9. Settings

    1. Shibboleth Integration
    2. Kimai Integration
  10. Staff Management

  11. Finance

  12. Pools Management

Clone this wiki locally