Skip to content

Setup Versio.io Managed

For all customers who want to run Versio.io in their own environment, Versio.io Managed is available.

Installation & Startup Package

Please carry out the installation by following the steps below:

  1. Verify server prerequisites
  2. Installation
  3. Customize configuration
  4. Startup Versio.io Managed
  5. Recommended activities after installation

Usefull activities to operate Versio.io Managed: 1. Shutdown Versio.io Managed 1. Backup & restore Versio.io Managed data

Prerequisites

Supported operating systems and sizing

The following operating systems are supported:

  • Ubuntu
  • Red Hat
  • Fedora
  • Debian

The following sizing depending on the usage is recommended: setup-system-requirements

Software components

The installer assumes that the following software components are already installed on the host:

  • TAR & GZip
  • WGET
  • OpenSSL (not necessary if own SSL certificates are available)
  • Docker & Docker Compose
    • Docker (>= version 20.10.0)
    • Docker-Compose (>= version 1.24.0)

Installation

Your Versio.io contact will provide you with a link to download the Versio.io Managed core. The installer can be downloaded and executed with the following commands. After the installation you will find the Versio.io application files in /opt/versio.io and the Versio.io data files in /home/versio.io.

wget -nv -N --no-check-certificate https://<my-link> // your get authentification from Versio.io contact

bash install.sh

Command: Download and install Versio.io managed core

Before the first start or when updates are available, the Docker images must be download once. With the following script the Docker images can be download. Please note that you must register for this in advance.

docker login repository.versio.io // your get authentification from Versio.io contact

bash pull-docker-images.sh

Command: Download Versio.io docker images

Customizing

Environment variable

The following environment variables can be set to accommodate customer specific wishes, when starting Versio.io:

Environment variable Purpose of use Description Default value
VERSIO_DOMAIN Web server config Define the URL domain address under which the Versio.io browser user interface can be accessed on the network. The domain address must match the domain specified in the SSL certificate, otherwise the browser will display an error message. Host name
VERSIO_PORT_HTTPS Web server config Define the port on which Versio.io can be accessed via HTTPS. 443
VERSIO_PORT_HTTP Web server config Define the port on which Versio.io should be accessible via HTTP. Please note that the HTTP has to be enabled in 'docker-compose.yml'. 80
VERSIO_VALIDITY_CERTIFICATE Self generated SSL certificates Validity of self-generated SSL certificates in days. 365
VERSIO_DATA Versio.io server and backup.sh Define the folder to store all Versio.io logging and database data. /home/versio.io
VERSIO_LOGGING_FOLDER Versio.io server Define the folder to store Versio.io logging data. /home/versio.io/log
VERSIO_BACKUP_FOLDER backup.sh Define the folder to store Versio.io backup data. /home/versio.io/backup
VERSIO_STAGE Versio.io server Define the stage and logging behavior of the Versio.io instance. If the value is not equal to production or loadtest, the amount of logged information is increased.

Configuration: Environment variables with default values

SSL certificate

The Versio.io startup script automatically generates an SSL certificate for HTTPS support if no certificate authority is available in the ./ssl folder (ca-root.pem and ca-private-key.pem).

For productive systems we recommend to store company specific SSL certificates in the ./ssl/versio.reverse-proxy folder of the startup script with following file names: * cert-private-key.pem for the private key * cert-public-key.pem for the public key

Please note that for self generated SSL certificates the certification authority 'ssl/ca-root.pem' should or must be made known on the client side:

  • Browser: Import of the certification authority into the certificate memory of the browser. If this is not done, you will receive a browser warning where you can again indicate that you accept the risk.
  • API usage: Announcement of the certification authority to the operating system or manual specification when starting the corresponding client application.

Startup

If the installation is finished, the Docker images are available and your customizing is ready, the Versio.io instance can be started:

bash startup.sh

Command: Start Versio.io instance

Enclosed is a sample output for starting a Versio.io instance:

Versio.io Managed Installer

Image: Versio.io Managed installer

After successful installation, we recommend that you perform the following activities as soon as possible:

  1. Login with the default user and password
  2. Configure SMTP server for e-mail notification (necessary for initial password set/reset!)
  3. Create new admin user (see Environment settings - User & rights)
  4. Deactivate default admin user
    • Change default password
    • Remove from default environment (see Environment settings - User & rights)
  5. Create a new environment (see Server settings - Environment settings)
  6. Invite new user to the new environment (see Environment settings - User & rights)
  7. Install an OneImporter (see Environment settings - OneImporter - Install)
  8. Configure OneImporter configuration (see Environment settings - OneImporter - Configurations)

Shutdown Versio.io Managed

To shut down a Versio.io instance the corresponding command must be executed:

bash shutdown.sh

Command: Stop Versio.io instance

Then, for example, updates of Versio.io Docker images or other maintenance work can take place before Versio.io is started again.

Backup & restore Versio.io Managed data

To backup a Versio.io server instance with all environment data the corresponding command must be executed (see environment varibale VERSIO_BACKUP_FOLDER):

bash backup-database-content.sh

Command: Backuup Versio.io instance includes all environment data

The backup script creates a physical backup with name versio.io-backup-<date>-<time>.tar.gz. Physical backups are performed by copying the individual data files or directories (see logical versus physical backups).

To ensure data integrity, the Versio.io Server instance is stopped, the backup is performed and the Versio.io Server instance is restarted. This means that during this time the Versio.io Server is not available. The downtime depends on the data volume to be backed up and is displayed at the end of the backup execution.

It is recommended to run the backup continuously e.g. based on cron jobs:

40 0 * * * /opt/versio.io/install/backup-database-content.sh

Configuration: Cronjob configuration for daily backup

To restore all Versio.io Managed data you can execute the follwoing script. Please note - All data of the current Versio.io Managed Instance will be overwritten!!!

bash /opt/versio.io/install/restore-database-content.sh <backup-date-time>

Configuration: Cronjob configuration for daily backup

Please note that a repocessing of the full-text search and topology detection reprocessing for each (!) environment must be performed when restoring backup data:

  • see Environment Settings - Full-text search - Reprocess environment
  • see Environment Settings - Topology detection - Reprocess environment