Upgrade Cerb5 without SVN

From Cerberus Helpdesk Wiki

It’s recommended you use SVN to update your Helpdesk whenever possible, but if you have no other choice a zipped build of Cerb5 is available. Since you need to outright replace your existing copy, it's a little trickier.

Prepare

Instead of overlaying the extracted zip files on top of the existing cerb5/ directory, move the old cerb5/ to the side and replace it with the new files. There's two benefits to doing it this way: one, by moving the old files to a new location you get the benefit of a temporary backup, and two, using completely new files ensures you get rid of any outdated code.

• Move your cerb5/ installation out of the way.
• Backup the database (because the structure can be modified on larger releases).
• Extract the new cerb5/ directory into the old path.
• Make sure APC is disabled. Cerberus has known issues with APC as well as many other php project.

Moving on... there's really only two things you need to hold onto when upgrading, the framework.config.php file and the storage/ directory. Although rare it's possible framework.config.php could change between versions, so you'll want to avoid simply replacing the file. Saving storage/ is vital because it holds all your attachments and any mail that hasn’t been parsed yet.

• Copy the database info from the top of your old framework.config.php, which includes the name, user and password.

• Administrators are sometimes required to add IP addresses to the framework.config.php file, so they can finish an upgrade or run a cron. Therefore if you included any unique IPs that you need to remember in the AUTHORIZED_IPS_DEFAULTS, copy those as well.

Note: Although it serves the same purpose, this IP list can be different from the one in System Settings.

Finish

• Swap the information you copied from before into the new framework.config.php file.
• Replace the storage/ directory.
• And finally re-adjust the file permissions if necessary. As usual check your httpd.conf file for the appropriate ‘User’ and ‘Group’ settings to replace apache:apache.

That’s it! If all went well, load up the Helpdesk in your browser and you should be taken to the login screen. Or if this was a larger update, the “click here to finish this upgrade” screen.

• When upgrading through significant changes, you may notice complaints about missing files or find deprecated features are still active. These are signs of an "incomplete" install which you can verify if the build and version don't match -- instead of 5.3.2 build 2010050101 you see 5.0.0 build 2010050101. In these cases, try clearing the cache of any old files.
• After you verify everything is working, you can remove the install/ folder (again) as it isn't needed for upgrades.
• If you need to keep a more "permanent" backup of the old version make sure you do that, otherwise you can also delete the original cerb5/ folder now.