Local Software Upgrades
| Table of Contents |
|---|
Upgrade Methods for Local Installs
...
Upgrades after 4.1.20 and up
The recommended upgrade method for local installations is a manual download of the latest version and running the associated upgrade script.
For upgrades consisting of multiple versions, ensure that each version upgrade is performed in order. If you have a particularly complicated upgrade or special concerns, contact our support team, and our engineers can recommend an upgrade strategy tailored to your situation and assist as needed.
If you have questions, need assistance, or wish You must be running at least 4.1.20 to follow any of the upgrade methods listed below. If you are not yet at this version, upgrade to 4.1.20 using the old upgrade process first, and then continue using the new upgrade process or contact support@6connect.com or any questions or to schedule an upgrade to the latest version.
There are now 3 different methods to run upgrades.
Old Method
, please contact support.
Manual Upgrade (Recommended)
A manual upgrade is the recommended route for local installations, providing the highest level of control and oversight, and may be performed in installation scenarios where company policies restrict automatic downloads / script executions :(See Upgrades prior to 4.1.19 for detailed instructions)
- Download the latest
...
- tar file from https://cloud.6connect.com/Download/Latest/
- Extract into web root.
Run configDir.sh ﹤web user﹥ from the command line as root in the web root. This will setup the directories apache user needs read/write access to.
Code Block language bash cd /var/www/html /var/www/html/configDir.sh <web user>
Run the upgrade scripts located in the upgrade/scripts directory in order of version number via
...
:
Code Block language bash php <upgrade-script.
...
php> -v
| Expand |
|---|
Command Line
In upgrade/scripts run 'php upgrade.php -h' to get the help and full usage of upgrade.php. This script will automatically get the latest tar file, create a backup, and run all the necessary upgrades between the current and latest version. The most common usage of upgrade will look like this 'php upgrade.php -v -b ﹤/path/to/store/backup﹥'
GUI
| ||
The following local upgrade options are available, but are not generally recommended - differences in installation setup and access levels may result in these options being less reliable than the manual upgrade option. GUIIn ProVision, navigate to Admin → Admin Settings page |
...
. If there is a new version available, an Upgrade button will be available. |
...
Click on the Upgrade Now button to go to the upgrade page. It will automatically download the latest version available, run all upgrade scripts, and create a log of the upgrade process. |
Upgrades prior and up to 4.1.19
IMPORTANT NOTE FOR 4.1.15 - The configDir.sh script must be run as root after the 4.1.15 tar file is unpacked and before running upgrade-4.1.15.php.
1. Create a database backup.
mysqldump -u ﹤user﹥ -p﹤pass﹥ ﹤6connect database name﹥ ﹥ /tmp/6connectDBBackup.﹤date﹥.sql
2. Create a directory backup. Even if you have offsite backup's with 6connect enabled, perform this step to ensure the most current data is saved.
tar -cvf 6connectFileBackup.﹤date﹥.tar /path/to/webroot
3. Move the tar file in 6connect web root.
tar -xof productionBuild-4.1.4.tar
This will place all the new files into your web root directory.
4. Run database upgrades, located in ./dev.
The simple rule of thumb is to run every database upgrade from the version after yours, to the version you want to get to. Here is the short cut list:
If upgrading from 4.1.0 or higher:
php upgrade-4.1.3.php -v
php upgrade-4.1.4.php -v
php upgrade-4.1.5.php -v
php upgrade-4.1.6.php -v
php upgrade-4.1.7.php -v
php upgrade-4.1.8.php -v
php upgrade-4.1.9.php -v
php upgrade-4.1.10.php -v
php upgrade-4.1.11.php -v
php upgrade-4.1.12.php -v
php upgrade-4.1.13.php -v
php upgrade-4.1.14.php -v
configDir.sh ﹤web user﹥ (after tar 4.1.15 tar file unpacked)
php upgrade-4.1.15.php -v
php upgrade-4.1.16.php -v
php upgrade-4.1.17.php -v
php upgrade-4.1.18.php -v
php upgrade-4.1.19.php -v
If upgrading from 3.9.3:
Contact 6connect Support - support@6connect.com
5. Check directory/file permissions for the following and make sure they read/write for the web user:
archive
keys
scans
zones
data/globals.php
images/custom
configDir.sh can be run to correct any permissions issues.
Check the imports directory for read/write permission in the configured php session dir.
6. Go to http://﹤web root﹥/configTest.php. If there are any configuration errors listed, they must be corrected.
7. Login and use!
Command LineIn upgrade/scripts run 'php upgrade.php -h' to get the help and full usage of upgrade.php. This script will automatically get the latest tar file, create a backup, and run all the necessary upgrades between the current and latest version. The most common usage of upgrade will look like this: 'php upgrade.php -v -b ﹤/path/to/store/backup﹥' |
...