Upgrading

Depending on what has changed since you deployed your server, you may need to perform one or more steps to do a clean upgrade to the latest code. Look for the following in the commit log (specifically, the files that were changed) when you update to the latest version of the repository:

If you see that SQL files or db_migrate.pl have changed, then you must do "Import Scheme" on 'Reality Main' in the "Setup / DB"->"Database" window of the application to update your database. If SQF files (game script) has changed, then you must rebuild your server from the application and copy the **Repository**\\deploy\\@reality_<id>.<world>\\ directory into ArmA2\ (where <id> and <world> are the values you specified when building). If configuration files and BattlEye anti-cheat files have changed in Repository\deploy\, you will need to backup and overwrite your existing versions of these files. Take care to change any default server names, passwords or similar back to their customized values after copying the new versions into your ArmA2 directory. If you receive an error like Cannot locate Some::Module.pm in @INC when trying to do anything in the application, you need to change the application's config file (RealityCP.exe.config) and make the "perl" value (where it says "done") empty, and then run the Set-up Perl again from the app.

These are the areas you will need to inspect to ensure a smooth upgrade. If database and code changes were not made at the same time and you do not read the history thoroughly, you may miss important changes and skip vital steps. It will save you frustration in the long run if you rebuild and redeploy, re-run the Reality Main scheme and check for any new or changed files in Repository\deploy\ whenever you would like to update.