README.md in lita-2.1.2 vs README.md in lita-2.2.0

- old
+ new

@@ -40,11 +40,11 @@ * Ruby 2.0 * Redis ## Installation -First, install the gem with `gem install lita`. This gives you access to the `lita` commmand. Run `lita help` to list available tasks. +First, install the gem with `gem install lita`. This gives you access to the `lita` command. Run `lita help` to list available tasks. Generate a new Lita instance by running `lita new NAME`. This will create a new directory called NAME (defaults to "lita") with a Gemfile and Lita configuration file. ## Usage @@ -293,11 +293,11 @@ zip_code: zip ) data = MultiJson.load(http_response.body) rep = data["representative"]["name"] - redis.set(zip, data["representative"]["name"]) + redis.set(zip, rep) rep end end Lita.register_handler(Representative) @@ -383,9 +383,13 @@ If you use `lita: true` instead of `lita_handler: true` in the metadata for your example group, only a small subset of Lita's RSpec extras will be enabled: * All Redis interaction will be namespaced to a test environment and automatically cleared out before each example. * Lita's logger is stubbed to prevent log messages from cluttering up your test output. * Lita's configuration is cleared out before each example, so that the first call to `Lita.config` will start from the default configuration. + +## Running as a daemon + +Lita has built-in support for daemonization on Unix systems. When run as a daemon, Lita will redirect standard output and standard error to a log file, and write the process ID to a PID file. To start Lita as a daemon, run `lita -d`. There are additional command line flags for specifying the path of the log and PID files, which override the defaults. If an existing Lita process is running when `lita -d` is invoked, Lita will abort and leave the original process running, unless the `-k` flag is specified, in which case it will kill the existing process. Run `lita help` for information about all the possible command line flags. ## Deploying to Heroku There are a few things worth mentioning when deploying an instance of Lita to Heroku: