WARNING This project is not maintained anymore. Please use ruote-sequel instead github.com/jmettraux/ruote-sequel

ruote storage implementation for DataMapper (dm) persistence

This is how a ruote engine is setup with a ruote-dm storage (postgres) and a worker :

require 'rubygems'
require 'json' # gem install json
require 'ruote'
require 'ruote-dm' # gem install ruote-dm

#DataMapper.setup(:default, 'sqlite3::memory:')
#DataMapper.setup(:default, 'sqlite3:ruote_test.db')
DataMapper.setup(:default, 'postgres://localhost/ruote_test')

engine = Ruote::Engine.new(
  Ruote::Worker.new(
    Ruote::Dm::Storage.new(:default)))

# ...

To create the tables in the database :

require 'dm-migrations'
Ruote::Dm::Document.auto_migrate!

Tested with dm 1.0.2, with the postgresql and the msyql adapters.

assuming you have

ruote/
ruote-dm/

• unit tests :

get into ruote/ and do

ruby test/unit/storage.rb -- --dm

• functional tests :

get into ruote/ and do

ruby test/functional/test.rb -- --dm

It works well on OSX, but test/functional/ct_2_cancel.rb is failing. Since OSX isn’t a often met server platform, we haven’t investigated further.

MIT

datamapper.org/

ruote.rubyforge.org/ github.com/jmettraux/ruote-dm

mailing list : groups.google.com/group/openwferu-users irc : irc.freenode.net #ruote