Before updating Foresight Mobile Platform at host server check if the conditions are satisfied:
Foresight Mobile Platform is installed.
All operations are executed using the account included into the Docker group.
The utilities unzip, wget and docker-compose are installed.
10 Gb or more free disk space.
Mobile platform server version and Relay server version match if the server was installed.
To update Foresight Mobile Platform 23.05, use the README.md file contained in the standalone_compose_files_v23.12.03.zip archive.
NOTE. To get the archive, contact technical support by sending a request to support@fsight.ru or via technical support services that are available after registration at the website.
Updating of other versions of Foresight Mobile Platform differs:
Previous logs will be unavailable on the Foresight Mobile Platform update.
IMPORTANT. To update Foresight Mobile Platform to the latest version, update the mobile platform to each later version one by one.
To update Foresight Mobile Platform 22.04:
Download new versions of images and files to mobile platform server. Unpack the archive:
% unzip standalone_compose_files_v22.04.<version number>.zip
Load new images to local storage:
% docker load -i standalone_images_v22.04.<version number>.tgz
After executing the operation the local storage will contain the files docker-compose.standalone.yaml and .env with the new version.
Change the SERVER_NAME parameter in the .env file if domain server name differs from localhost:
SERVER_NAME = <IP address or DNS server name>
To specify several server names, use the space character, for example:
SERVER_NAME = 127.0.0.1 localhost
Open the update_standalone.py file and set parameters:
OLD_VERSION_COMPOSE_PATH. Specify path to the files docker-compose.standalone.yaml and .env with the old version.
NEW_VERSION_COMPOSE_PATH. Specify path to the files docker-compose.standalone.yaml and .env with the new version.
UP_TIMEOUT. If required, set timeout in seconds after the start of the new mobile platform version to the start of loading files to MinIO.
The example of the update_standalone.py file with the specified parameters:
py
OLD_VERSION_COMPOSE_PATH=./old_version
NEW_VERSION_COMPOSE_PATH=./new_version
File structure corresponding to the parameters specified in the example:
~
│
└───old_version
│ │ docker-compose.standalone.yaml
│ │ .env
│
└───new_version
│ docker-compose.standalone.yaml
│ .env
│ update_standalone.py
Start the update_standalone.py file for execution in Python 3.6 or later:
python3 update_standalone.py
After executing the operations the message about successful file loading to MinIO is displayed, and Foresight Mobile Platform will be updated to the latest version.
To update Foresight Mobile Platform 21.04:
Download new versions of images and files to mobile platform server. Unpack the archive:
% unzip standalone_compose_files_v21.04.01.zip
Load new images to local storage:
% docker load -i standalone_images_v21.04.01.tgz
After executing the operation the local storage will contain the files docker-compose.standalone.yaml and .env with the new version.
Open the update_standalone.py file and set parameters:
OLD_VERSION_COMPOSE_PATH. Specify path to the files docker-compose.standalone.yaml and .env with the old version.
NEW_VERSION_COMPOSE_PATH. Specify path to the files docker-compose.standalone.yaml and .env with the new version.
UP_TIMEOUT. If required, set timeout in seconds after the start of the new mobile platform version to the start of loading files to MinIO.
The example of the update_standalone.py file with the specified parameters:
py
OLD_VERSION_COMPOSE_PATH=./old_version
NEW_VERSION_COMPOSE_PATH=./new_version
File structure corresponding to the parameters specified in the example:
~
│
└───old_version
│ │ docker-compose.standalone.yaml
│ │ .env
│
└───new_version
│ docker-compose.standalone.yaml
│ .env
│ update_standalone.py
Start the update_standalone.py file for execution in Python 3.6 or later:
python3 update_standalone.py
After executing the operations the message about successful file loading to MinIO is displayed, and Foresight Mobile Platform will be updated to the latest version.
To update Foresight Mobile Platform 20.10 or earlier, and also the Docker subsystem deployed on the server:
Go to the directory with the file docker-compose.standalone.yml of the current host server installation and stop the current platform version:
% docker-compose -f docker-compose.standalone.yml down
After successful platform stop delete the existing images:
% docker image rm $(docker image ls -q)
Delete previous installation files:
.env.
docker-compose.standalone.yml.
Download new versions of images and files to mobile platform server. Unpack the archive:
% unzip compose_files_v20.10.06.zip
Load new images to local storage:
# load
% docker load -i fmp_v20.10.06.tgz
# delete archive
% rm -rf fmp_v20.10.06.tgz
Execute commands for successive update of Foresight Mobile Platform from the 18.04 version to the 19.03 version:
NOTE. Product update is available from version 18.04. When updating Foresight Analytics Platform from the 19.03 version to the 20.10 version skip this step.
On platform update from version 18.04 to version 18.09:
% docker-compose -f docker-compose.standalone.yml run --rm -u root hhive sed -i 's|/var/hhive/static|/var/hh_static/static|g' /var/hhive/nginx/includes/dashboard.inc
On updating the product from 18.09 to 18.12 version and from 18.12 to 19.03 version:
% docker-compose -f docker-compose.standalone.yml run --rm hhive bash -c 'mkdir -p /var/hhive/ssh/ /var/hhive/supervisor/ && touch /var/hhive/ssh/ssh_conf_relay /var/hhive/supervisor/supervisor_ssh.conf'
Execute the command to delete static elements of the previous build:
% docker volume rm hyperhive_var_static
Update version of Foresight Mobile Platform:
% docker-compose -f docker-compose.standalone.yml up
After executing the operations, Foresight Mobile Platform will be updated to the latest version.
See also:
Installing and Setting Up Foresight Mobile Platform | Managing Mobile Platform