Ernie

By Tom Preston-Werner ([email protected])

WARNING: This software is alpha and should not be used in production without extensive testing. You should not consider this project production ready until it is released as 1.0.

Description

Ernie is a BERT-RPC server implementation that uses an Erlang server to accept incoming connections, and then delegates the request to a Ruby handler via Erlectricity.

Ernie currently supports the following BERT-RPC features:

call requests
cast requests

Installation

You must have Erlang installed before installing Ernie.

$ gem install ernie -s http://gemcutter.org

Running

Usage: ernie [command] [options]
    -h, --handler HANDLER            Handler file
    -p, --port PORT                  Port
    -n, --number NUMBER              Number of handler instances
    -d, --detached                   Run as a daemon
    -P, --pidfile PIDFILE            Location to write pid file.

Commands:
  <none>                Start an Ernie server.
  reload-handlers       Gracefully reload all of the the ruby handlers
                        and use the new code for all subsequent requests.
  stats                 Print a list of connection and handler statistics.

Examples:
  ernie -d -p 9999 -n 10 -h calc.rb
    Start the ernie server in the background on port 9999 with ten
    handlers, using the calc.rb handler file.

  ernie reload-handlers -p 9999
    Reload the handlers for the ernie server currently running on
    port 9999.

Example Handler

require 'ernie'

mod(:calc) do
  fun(:add) do |a, b|
    a + b
  end
end

Example BERT-RPC call for above example

-> {call, calc, add, [1, 2]}

<- {reply, 3}

Using the BERTRPC gem to make calls to Ernie

You can make BERT-RPC calls from Ruby with the BERTRPC gem:

require 'bertrpc'

svc = BERTRPC::Service.new('localhost', 8000)
svc.call.calc.add(1, 2)
# => 3

Contribute

If you'd like to hack on Ernie, start by forking my repo on GitHub:

http://github.com/mojombo/ernie

To get all of the dependencies, install the gem first. The best way to get your changes merged back into core is as follows:

Clone down your fork
Create a topic branch to contain your change
Hack away
Add tests and make sure everything still passes by running rake
If you are adding new functionality, document it in the README.md
Do not change the version number, I will do that on my end
If necessary, rebase your commits into logical chunks, without errors
Push the branch up to GitHub
Send me (mojombo) a pull request for your branch