-
Notifications
You must be signed in to change notification settings - Fork 260
Upgrading a BrowserCMS project
peakpg edited this page Mar 14, 2012
·
33 revisions
- This guide assumes you are upgrading a BrowserCMS project to 3.4.x from 3.3.x.
- See below for a list of instructions for older versions.
- It assumes the project is currently running on Rails 3.0 and will be updated to Rails 3.1 as part of this process.
- The project being managed using Git (or other SCM)
Ensure you have the correct version:
$ bcms -v
Should return BrowserCMS 3.4.0
or some other 3.4.x version.
In your project, run the following script from the command line:
$ bcms-upgrade project
This will update the project to use the new version of the gem, add new migrations and seed data as needed. You will then need to run the following commands:
$ rake rails:update
Then do the following:
- Review the following files and ensure the specified lines appear (use Git to selectively discard the changes):
config/environment/development.rb => Should contain:
SITE_DOMAIN=localhost:3000
config/environment/production.rb
SITE_DOMAIN=http://your-site-domain.com
config.action_controller.page_cache_directory = File.join(Rails.root, 'public', 'cache')
config.action_mailer.smtp_settings = {:address => 'mail.yourmailserver.com', :domain => "#{SITE_DOMAIN}"}
config/environment/test.rb
SITE_DOMAIN=localhost:3000
- Run
git checkout config/routes.rb
to revert this file - Run
rake db:migrate
to migrate the database
If you need instructions for how to upgrade earlier versions of BrowserCMS, see the following list: