Zeus, QC and NOT using DATABASE_URL causes tests to break

[pjammer]

So, i have an initializer using:

require 'queue_classic'
QC::Conn.connection = ActiveRecord::Base.connection.raw_connection

With the only change to my app of running Zeus, and running zeus rake I see that this error now appears. I went with the initializer approach, as I once used the DATABASE_URL env variables, but fixtures wouldn't load.

test_should_create_a_staffer(StaffsControllerTest):
ArgumentError: missing QC_DATABASE_URL or DATABASE_URL
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/conn.rb:106:in `db_url'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/conn.rb:89:in `connect'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/conn.rb:68:in `connection'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/conn.rb:13:in `block in execute'
    <internal:prelude>:10:in `synchronize'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/conn.rb:9:in `execute'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/queries.rb:8:in `block in insert'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic.rb:78:in `log_yield'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/queries.rb:6:in `insert'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic/queue.rb:11:in `enqueue'
    /Users/nerb/.rvm/gems/ruby-1.9.3-p392-railsexpress/gems/queue_classic-2.1.4/lib/queue_classic.rb:61:in `method_missing'

Thoughts?

[senny]

Using the AR connection is not completely working at the moment. See the discussion in #96. I am working on it though. See #134 to follow the progress.

For the time being it's better to use QC_DATABASE_URL.

[smathieu]

@pjammer I had the same issue with Zeus. You can fix it by adding a custom plan, which tells zeus how to boot unsupported gems. Here's how mine looks like:

require 'zeus/rails'

class CustomPlan < Zeus::Rails

  # def my_custom_command
  #  # see https://github.com/burke/zeus/blob/master/docs/ruby/modifying.md
  # end
  def after_fork
    super
    begin
      load File.join(File.dirname(__FILE__), 'config/initializers/queue_classic.rb')
    rescue ActiveRecord::ConnectionNotEstablished
    end
  end

end

Zeus.plan = CustomPlan.new

And the zeus.json file

{
  "command": "ruby -rubygems -r./custom_plan -eZeus.go",

  "plan": {
    "boot": {
      "default_bundle": {
        "development_environment": {
          "prerake": {"rake": []},
          "runner": ["r"],
          "console": ["c"],
          "server": ["s"],
          "generate": ["g"],
          "destroy": ["d"],
          "dbconsole": []
        },
        "test_environment": {
          "cucumber_environment": {"cucumber": []},
          "test_helper": {"test": ["rspec", "testrb"]}
        }
      }
    }
  }
}

More info here: https://github.com/burke/zeus/blob/master/docs/ruby/modifying.md