Versio.io Managed operation¶
Startup¶
If the installation is finished, the Docker images are available and your customizing is ready, the Versio.io instance can be started:
Command: Start a Versio.io instanceBelow is a sample output for starting a Versio.io instance:

Image: Versio.io Managed installer
Status¶
Get a detailed status of the operational environment and execution status of the Versio.io platform:
Command: Status of the Versio.io platformShutdown¶
To shut down a Versio.io instance, the following command must be executed:
Command: Stop a Versio.io instanceThen, for example, updates of Versio.io Docker images or other maintenance work can take place before Versio.io is started again.
Update¶
It is recommended to make a backup before each update!
To update a Versio.io Managed instance, the following commands should be executed in the /opt/versio.io/install folder as the versio user:
If the application stack and the database of the Versio.io platform are operated on separate server instances, the update should be carried out as follows:
# LOGIN APP STACK HOST!
# Shutdown app stack
bash shutdown.sh
# SWITCH TO DATABASE HOST!
# Update database stack
bash update.sh
# SWITCH TO APP STACK HOST!
# Update app stack
bash update.sh
Command: Update a Versio.io Managed instance with separate app and database stacks
Update AI content¶
Versio.io provides artificial intelligence (AI) content for the assessment of product lifecycles and vulnerabilities. This content changes daily and should therefore be updated daily. We recommend running the update as a cron job.
# Update the artificial intelligence content repositories (product, lifecycle, vulnerability etc.)
bash /opt/versio.io/install/utils/update-ai-rep.sh
# Cron job to update the artificial intelligence content repositories every day. Please configure it for user 'versio'!
0 6 * * * /bin/bash /opt/versio.io/install/utils/update-ai-rep.sh > /opt/versio.io/install/utils/update-ai-rep.log 2>&1
Attention
Run the script or cron job as the versio user on the standalone or application host (see configuration of environment variable VERSIO_DEPLOYMENT_PROFILE).