Skip to content
Matthias Hecker edited this page Mar 9, 2015 · 5 revisions

With the adoption of my fork 4poc/rbot (fork branch) a few noteworthy things have changed:

  • Dropped support for ruby <= 1.8.3, now requires at least ruby >= 1.9.3.
  • Removes broken/outdated plugins.
  • Removes DRb remote interface (DRuby interface) due to security concerns.
  • Introduces a new web service.
  • Registry: Dropped support for ruby-BDB (bdb is supported through DBM).
  • Registry: Refactored adapters and introduces DBM, daybreak and sqlite as alternatives.
  • Registry: New standalone backup/restore script for registry databases helps with migration and backups.
  • Registry: The registry folder now has a postfix based on the adapter used: ~/.rbot/registry_<FORMAT>.

Migration Guide

  • Make sure to fulfill its dependencies, see the install guide for help.
  • Stop any running rbot.
  • Fetch the latest version of rbot into a new directory:
git clone git://github.com/ruby-rbot/rbot.git rbot_new/
  • Backup the profile data directory: cp -R ~/.rbot ~/.rbot_backup
  • Migrate the database registry if necessary using the new rbotdb command:

For instance if you used bdb before, first create a backup:

% ruby ~/rbot_new/bin/rbotdb backup -t bdb -p ~/.rbot
[...]
Written registry to ./backup_2014-03-06_133203.rbot

This creates a platform independent backup file (.rbot) that you can restore later using any other supported database adapter, for instance tokyocabinet:

% ruby(1.9) ~/rbot_new/bin/rbotdb restore -t tc -f ./backup_2014-03-06_133203.rbot
[...]
Restore successful!

You should run the backup command in the original environment, so if you run your bot in 1.8.7 with BDB and want to migrate to the latest version, first create a backup file using the rbotdb utility within this environment. Then switch to the new environment (with ruby 2.1.1 and tokyocabinet installed for instance) and restore with rbotdb restore.

  • Change the configuration to reflect the change in the used database adapter. Open up ~/rbot/rbot.conf and change:
core.db: bdb

to:

core.db: tc

If there is no core.db present, just add it to the end of the file.

  • Run Rbot as usual using cd ~/rbot_new; ruby launch_here.rb

Consult this page for a more detailed explanation of rbots database adapters.

Clone this wiki locally