Always when updating a Roxen installation, remember shut down the server during the update session to avoid any errors from occuring.
Windows Binary Update
Updating a Windows installation follows the same procedure as for the Windows installation. Within the wizard, specify the current location of the installation. Roxen will now be installed anew, by overwriting all the old files. Configurations files and files created by others than the installation program will not be overwritten. However, be adviced to make copies of any Roxen file that you have modified, else the information will be lost.
Unix Binary Update
The installation script takes a number of options; use --help to list them. For instance, --without-start makes sure Roxen will not start after the update is complete.
It will take a while for the script to extract the Pike binary and start the real installation script. When it has finished it will prompt for the location of your current installation:
Enter the path to your current Roxen installation. Remember not to add "roxen" to the path since the installation script itself adds "roxen" to the path. The script will install the new version of Roxen in roxen/server-2.1.[build]/. The first time Roxen is installed this directory is called roxen/server/. This directory will be renamed to roxen/server-old/ when Roxen has been updated.
Enter the path to your current Pike installation. Pike will be installed in a versioned directory, e.g. pike/7.0.[build]/.
Take care not to keep any essential code in your old roxen/server/ directories. After three updates Roxen begins deleting old server directories. Keep vital code in your roxen/local/modules/ directory instead. After each update, make sure any local changes in the old Roxen-source is moved to the new roxen/server/ directory.
Unix Source Update
The result when updating a Roxen installation compiled from the source is the same as when updating a binary installed Roxen. What differs however is the procedure.
Follow the instructions in the installation manual but only through the first three commands as you already have a configurations interface available.