If you have previously installed COmanage Match, follow these steps to upgrade your installation.

Always Upgrade QA First

It is recommended that you maintain separate QA (test) and Production instances. Upgrade your QA tier and confirm things are working as expected before upgrading Production.

Review Installation Instructions

You should review the general installation instructions to check for any changes to minimum version (eg: minimum PHP version) and other requirements. 

Backup Your Database

While upgrading is usually a fairly straightforward process, from time to time fairly significant database changes are made. Efforts are made to make these changes transparent, but as a precaution you should create a backup of your database prior to upgrading in case you need to revert the upgrade.

Download New Source

  1. Checkout the source as described Match Installation - Source.
  2. Copy your local directory from your previous installation, or symlink to it.

Run UpgradeVersion Command

The UpgradeVersion Command handles various tasks related to updating the database state for the application, including updating any table definitions and performing simple data migrations. You may need to run this command as a user that has permission to write to your tmp directory.

$ cd app
$ ./bin/cake upgradeVersion
$ ./bin/cake cache clear_all

(warning) Prior to Match v1.2.0, there was no upgradeVersion command. When upgrading to a version prior to v1.2.0, use ./bin/cake database instead.

UpgradeVersion When Tracking develop

For deployments tracking the develop branch, it is generally safe (and desirable) to run upgradeVersion each time the codebase is updated, unless there is a version specific upgrading note with instructions to the contrary.

Version Specific Upgrade Steps

Run the appropriate steps for the versions you are upgrading past AND to. For example, if you are upgrading from v1.0.0 to v1.2.0, you must run the upgrade steps for both v1.1.0 and v1.2.0 (if any).