Migrate to 1.4.0

Note: Version 1.4.0 was not released yet.

Version 1.4.0 added a registry of meetings, custom advanced options for rooms (config.xml) and a few other things.

Use this guide to migrate from 1.3.x to 1.4.0.

Migration

Generate the new migration and apply it:

bundle exec rails generate bigbluebutton_rails:install 1.4.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.

Views

No views were added in this version. One view was removed and can be removed from your application:

app/views/bigbluebutton/rooms/external.html.erb

New dependencies

Add to your Gemfile:

gem 'strong_parameters'
gem 'resque'
gem 'browser'

Cron job

Check the new config/schedule.rb file and add the new tasks to your application's schedule.rb.

Database

MySQL is now officially the database used for development, testing and production. Consider using it.

Resque

BigbluebuttonRails now uses resque to find out when meetings started to create a registry of meetings. It uses tasks inside a queue named bigbluebutton_rails.

So make sure that both in your production server you have resque always running. You can start it with:

rake resque:work QUEUE='bigbluebutton_rails'

You need it in development also if you want to keep track of meetings that happened.

Resque and Resque-scheduler use {redis}[http://redis.io/] to store their data, so you will need it in your server. If you're on Ubuntu, you can install it with:

apt-get install redis-server