Migrate to 2.0.0

Version 2.0.0 is the first version for Rails 4 and ruby 2. It adds few changes, mostly the use of the createTime parameter in join calls and separation of passwords used in API calls from passwords defined by the users. See the CHANGELOG for more details.

Use this guide to migrate from 1.4.x to 2.0.0.

Migration

Generate the new migration and apply it:

$ bundle exec rails generate bigbluebutton_rails:install 2.0.0 --migration-only
$ bundle exec rake db:migrate

Locales

Copy the new locale file config/locales/en.yml to your application replacing the old one.

Dependencies

You don't need to require the dependencies in your Gemfile anymore, they are required by the gem.

If you're not using these gems directly in your application, you can remove them from your Gemfile:

gem 'strong_parameters' # Rails 4 includes it automatically
gem 'resque'
gem 'browser'
gem 'whenever' # not a dependency anymore

Cron jobs

The dependency on the gem Whenever was removed. So the files it used can also be removed.

If not in use by your application, you can remove the files:

• config/schedule.rb

Resque-scheduler

BigbluebuttonRails now uses resque-scheduler instead of Whenever to schedule background jobs.

This gem usually reads the schedule of workers from a yml file. This file can be put at config/workers_schedule.yml, for example. If you don't have it in your application, create it, and then add the contents of config/resque/workers_schedule.yml to it.

Make sure you read the documentation of resque-scheduler to see how to load the schedule file into the gem.

Then you can start the scheduler with:

$ bundle exec rake resque:scheduler

Update the recordings

The structures in which recordings are stored in the database changed, so we need to fetch recordings again from the web conference servers to update the database. This will happen periodically (check your crontab), but you can do it now to prevent problems.

$ bundle exec rake bigbluebutton_rails:recordings:update