-
Notifications
You must be signed in to change notification settings - Fork 259
Upgrading a BrowserCMS project
One of the goals for the BrowserCMS project is to make upgrades as easy as possible. We provide some built in tools to help make this easier (like bcms upgrade) but due to the custom nature of each project, there will likely be some manual steps that will require review. In particular, upgrading BrowserCMS will also tend to require updating to a newer version of Rails, which has its own set of challenges.
Before getting started, take note of what version of BrowserCMS and Rails you are currently running. Then consult section 4 below and find the most relevant instructions for your upgrade. The 'safest' option is probably to upgrade completely one step at a time (i.e. 3.3.x -> 3.4.x, then 3.4.x -> 3.5.x), but that will certainly take more time than just skipping a version.
- Back up your database
- Use an SCM (ideally Git)
- Work in development first, with copy of production data
This should probably go without saying, but upgrades can be risky. New versions of BrowserCMS may involve adding migrations, changing existing data and altering files.
Using a Source Control system is essential (and hopefully you are already doing it). Git will work best, as many of the upgrade scripts will automatically revert files using Git. It's a good idea to start with a clean working directory, so you can revert changes made.
It's ideal to test these migrations on a copy of the database, with a matching copy of the uploads directory first. This will allow you to compare files to make sure they exist and are displaying correctly after the migrations run.
Based on what version of BrowserCMS you want to upgrade to (and from), see the following list: