statusz 0.0.4 → 0.1.0.pre

data/.gitignore

@@ -1 +1,4 @@
 *.gem
+/doc/
+/.yardoc/
+/Gemfile.lock

data/.yardopts

@@ -0,0 +1 @@
+--no-private --protected --markup=markdown -- lib/**/*.rb

data/README.md

@@ -1,37 +1,44 @@
-statusz
-=======
+# statusz
 
-statusz is a Ruby tool to write out git information when you deploy. It is useful if your project meets the
-following criteria:
+statusz is a simple Ruby tool to display deploy-time and runtime server information. It is useful if your
+project meets the following criteria:
 
 * It lives in git.
 * It's deployed using some kind of unix-y OS.
-* It uses some kind of ruby-based deployment system.
-* It is a web server that can serve up web pages (not strictly necessary; if this isn't the case, statusz can
-  write out a plain text file for you instead).
+* It uses some kind of ruby-based deployment system (not strictly necessary)
+
+It is especially useful if your project is a web server, but this isn't necessary.
 
 statusz helps you quickly tell what version of the code is actually running on your server, and who most
 recently deployed it. It's particularly useful in environments where developers deploy the code.
 
-Installation
-------------
+## Installation
 
     gem install statusz
 
-statusz requires Ruby -- it's tested with 1.9.2, but probably works with 1.8.7 and 1.9.3 and many other
+statusz requires Ruby -- it's tested with 1.9.3, but probably works with 1.8.7 and 1.9.2 and many other
 versions as well.
 
-Usage
------
+## Usage
 
-``` ruby
-# Somewhere in your deploy scripts, probably where you stage the files before you rsync them:
-require "statusz"
-Statusz.write_file("#{your_staging_root}/statusz.html")
-```
+First, decide how you are going to use statusz. There are two parts to statusz: a method that you call from
+your deployment scripts (`Statusz.write_file`) that writes out some deploy-time information (date, current
+user, and git information) to a file. Then, there is a server component. You can either use
+`Statusz.render_from_json` directly in a web app, or use the rack application `Statusz::Server` to serve
+statusz pages.
 
-Now you can serve up the file from your webserver however you like. If you have a public folder, you can drop
-the file in there. Here's how we serve it from one of our sinatra servers:
+You may use either the deployment or the server parts of statusz, or both.
+
+**Using the deploy component without the runtime component**
+
+You may wish to use statusz in your deployment, but not in your server (for example, if your application is
+not written in Ruby, or is not a web server, or if all the status information you wish to display is available
+at deploy time). In this case, you can just write out a flat file at deployment time and ship it with the rest
+of your application. Write out a text file (`:format => :text`) if your application will not serve the status
+(that way it will sit on the app server where someone can easily find it and inspect it). If your application
+can serve static html, write out an html file (`:format => :html`) and then serve it in your app:
+
+Here's how we serve it from one of our sinatra servers:
 
 ``` ruby
 get "/statusz" do
@@ -40,10 +47,57 @@ get "/statusz" do
 end
 ```
 
+See "Deployment", below, for more information about using the `Statusz.write_file` method.
+
+**Using the runtime component without the server component**
+
+You might choose to use only the runtime components of statusz if you only want to display runtime information
+on your status page. There are two different ways to use statusz at runtime: you can either make use of the
+`Statusz.render_from_json` method, or use the `Statusz::Server` Rack application. In either case, you'll want
+to set `filename = nil` to indicate that there is no deploy-time information available.
+
+See "Runtime", below, for more information about `Statusz.render_from_json` and `Statusz::Server`.
+
+**Using statusz in both your deployment and at runtime**
+
+You can use both parts of statusz together to display both deploy-time and runtime status information. If you
+do this, you'll need to write out a json-formatted statusz file at deploy time:
+
+``` ruby
+Statusz.write_file("statusz.json", :format => :json)
+```
+
+and then use that file at runtime:
+
+``` ruby
+Statusz.render_from_json("./statusz.json", :html, :db_host => "dbslave1.example.com")
+# or
+Statusz::Server.new("./statusz.json",:db_host => "dbslave1.example.com")
+```
+
+See "Deployment" and "Runtime" below for more information.
+
+### Deployment
+
+Statusz writes out deploy-time information with `Statusz.write_file`. This can take a few options, but it has
+sensible defaults.
+
+``` ruby
+# Somewhere in your deploy scripts, probably where you stage the files before you rsync them:
+require "statusz"
+Statusz.write_file("#{your_staging_root}/statusz.html")
+```
+
+This writes out a single flat html file, `statusz.html`, which you can ship with your app (if you're not using
+the runtime server components of statusz -- see below).
+
+Now you can serve up the file from your webserver however you like. If you have a public folder, you can drop
+the file in there.
+
 If you want statusz to write a plain text file or json instead of an html file, you can do that:
 
 ``` ruby
-Statusz.write_file("statusz.txt", :format => :text)
+Statusz.write_file("statusz.txt", :format => :text) # or :format => :json
 ```
 
 If you're deploying a commit other than HEAD of the current branch, you can give statusz a treeish
@@ -70,31 +124,47 @@ Here are the possible fields -- by default, statusz will write them all:
 * `"git user info"` -- The user name and email in git
 * `"all commits"` -- A list of all ancestors of the latest commit. In the html version, it's a search box.
 
-Finally, statusz can write out extra arbitrary fields if you want. Just attach a hash of objects that have
+Finally, `Statusz.write_file` can write out extra arbitrary fields if you want. Just attach a hash of objects that have
 meaningful `to_s` representations:
 
 ``` ruby
 Statusz.write_file("statusz.html", :extra_fields => { "database host" => "dbslave3.example.com" })
 ```
 
-Options
--------
+### Runtime
 
-The only method provided by statusz is `Statusz.write_file(filename = "./statusz.html", options)`. Here is a
-full list of possible `options`:
+If you want to display some status information that is only available at runtime, then you can use one of
+statusz's two runtime components. **In either case, you'll need to write a json-formatted statusz file in your
+deployment, or else not write any statusz file at deploy time.**
 
-* `:format` -- one of `:html`, `:text`, `:json` (defaults to `:html`).
-* `:fields` -- an array; some subset of `["git directory", "latest commit", "containing branches", "date", "current
-  user on deploy host", "git user info", "all commits"]` (defaults to the whole thing).
-* `:extra_fields` -- a hash of arbitrary keys and values that will be stringified. You can override values in
-  `:fields` if you wish.
+If your application is a Ruby web server, you can serve statusz pages at (e.g. at `/statusz`) using the
+`Statusz.render_from_json` method.
 
-Screenshot
-----------
+Here's how you might do this in a Sinatra server:
 
-![screenshot](http://i.imgur.com/hjNvH.png)
+``` ruby
+get "/statusz" do
+  db_host = get_db_host_info[0] # Some dynamic information
+  Statusz.render_from_json("./statusz.json", :html, "db host" => db_host)
+end
+```
+
+See the `example/` directory for a small Sinatra application that further illustrates this usage.
 
-TODO
-----
+The other option, useful if your project is not a web application (or not written in Ruby) is to use the
+`Statusz::Server` rack application. You instantiate the app with your `statusz.json` file and any extra
+runtime parameters you wish to include; it will then serve requests with the appropriate statusz page.
+`Statusz::Server` looks at file extensions to determine the output format, so if the request ends in `.json`,
+it serves the json-formatted statusz, and similarly for `.txt` and `.html`. (Default is html, if there is no
+suffix.)
 
-* Call via command-line script? Useful if doing a non-ruby deploy.
+See `rack_example/` for a small example of a `Statusz::Server` application.
+
+## Documentation
+
+Besides this document, you can see a couple of small examples in `example/` and `rack_example/` and you may
+also consult the [method-level documentation](http://rubydoc.info/github/ooyala/statusz/master/frames).
+
+## Screenshot
+
+![screenshot](http://i.imgur.com/hjNvH.png)

data/example/Gemfile

@@ -0,0 +1,4 @@
+source :rubygems
+
+gem "sinatra"
+gem "thin"

data/example/Gemfile.lock

@@ -0,0 +1,24 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    daemons (1.1.4)
+    eventmachine (0.12.10)
+    rack (1.4.1)
+    rack-protection (1.2.0)
+      rack
+    sinatra (1.3.3)
+      rack (~> 1.3, >= 1.3.6)
+      rack-protection (~> 1.2)
+      tilt (~> 1.3, >= 1.3.3)
+    thin (1.3.1)
+      daemons (>= 1.0.9)
+      eventmachine (>= 0.12.6)
+      rack (>= 1.0.0)
+    tilt (1.3.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  sinatra
+  thin

data/example/README.md

@@ -0,0 +1,13 @@
+This is a small demo app that shows how to write out deploy-time information to a `statusz.json` file and then
+add some additional runtime information and serve both html and json statusz pages from a simple web server.
+
+First, you can generate the `statusz.json` if you want (there's already a copy checked in):
+
+    $ ./generate_statusz_json.rb
+
+This just shows how you would generate the json file from your deploy scripts.
+
+Next, run the web server:
+
+    $ bundle install
+    $ bundle exec ruby sample_app.rb

data/example/generate_statusz_json.rb

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+# This script imitates the code that would live in a deploy. It generates the statusz.json file that is used
+# by the server.
+
+# Use the local version of statusz. In your app, you would just 'require "statusz"'.
+$:.unshift File.join(File.dirname(__FILE__), "../lib")
+require "statusz"
+
+Statusz.write_file "./statusz.json", :format => :json

data/example/sample_app.rb

@@ -0,0 +1,52 @@
+require "sinatra"
+
+# Use the local version of statusz. In your app, you would just 'require "statusz"'.
+$:.unshift File.join(File.dirname(__FILE__), "../lib")
+require "statusz"
+
+get "/" do
+  erb :index
+end
+
+get "/statusz.:format" do
+  case params[:format]
+  when "html"
+  when "json"
+    content_type :json
+  else
+    halt 404, "No such page."
+  end
+  # Generate some dynamic content:
+  db_host = "dbslave#{Random.rand(4)}.example.com"
+
+  # Include it in our statusz output:
+  Statusz.render_from_json("./statusz.json", params[:format].to_sym, "db server" => db_host)
+end
+
+__END__
+
+@@ index
+<html>
+  <head>
+    <title>Sample Statusz App!</title>
+    <style>
+      body {
+        background-color: #444;
+        color: #eee;
+        font: 18px "HelveticaNeue-Light", "Helvetica Neue Light", "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif;
+        text-align: center;
+        margin: 0;
+        padding: 50px;
+      }
+      a {
+        text-decoration: none;
+        border-bottom: 1px solid #fff;
+        color: #fff;
+      }
+    </style>
+  </head>
+  <body>
+    This is an example of a web app that uses statusz. Go to <a href="/statusz.html">statusz.html</a> or
+    <a href="/statusz.json">statusz.json</a> to see it in action.
+  </body>
+</html>

data/example/statusz.json

@@ -0,0 +1 @@
+{"git directory":"statusz","latest commit":"2ce6199c7502d18105512d048eb01b550e72f734","containing branches":"master","date":"2012-10-23 11:51:07 -0700","current user on deploy host":"caleb","git user info":"Caleb Spare <caleb@ooyala.com>","all commits":"2ce6199c7502d18105512d048eb01b550e72f734\n14cf085f9ebb64e661b78c68a5d17e758aa15147\n0b43212a1ba8727cfdc969ef9221526cd3e161ea\n5424998dd84dd952a98456b47edcd92910dd2d10\n8c370aa8e0c75377a3076f49acb0091867940e31\n20b09ce2a7dc3815a89b5b2a62f51a4a5d1b5ec6\na45ba55442b8f255a0dec124c5a14be8c4e87205\n7dae9155b2ded641d7c766a34240e9243d2c8ca6\n16bbab8ce8cccb0c9287ae0777400216e21f0c96\n3acdd8e33d319083f77e7e8838cda9578b76b00a\nccc8a28ff66c658fe52350b8c03e6a82010e64cf\n3ac95f0ad62ea05d8e378e0a1287f0c8d5cc58ff\n12c78bb369af9d4e468e0c17df2aa8d354a7e45e\n9e4baa9d354b43e11fa5919db9801a2fbb15cec4\nb97091a3f59136b539846728a65d691986e6e54f\nf27d782a6a1bc0d2e8b5b9e2bf3e9eddb5d04cf6\n18fec163be18bb7ba13ebea269d44c35f3e1ea9c\n1e4a55212cf966e03442ab5da3fb72686eee7a22\na85c9b89bf642601ea8138dee978f6ea8302b4bf\nc8e543b9d434971d8cecdf577873a303bf6fb464\n96831b4a27b3c471c3d251406cffa62c552f2dc5\nd389dc833162d09e66220ac47fabf441ca61f45e\n896fe2c83240c8493acc4a769379125307ac3d98"}

data/lib/statusz.rb

@@ -2,8 +2,11 @@ require "cgi"
 require "erb"
 require "time"
 require "json"
+require "rack"
 
+# Statusz is a tool for displaying deploy-time and runtime server information.
 module Statusz
+  # @private
   FIELD_TO_SCRAPING_PROC = {
     "git directory" => Proc.new { |commit| `git rev-parse --show-toplevel`.strip.rpartition("/").last },
     "latest commit" => Proc.new { |commit| `git log --pretty=%H #{commit} -n 1`.strip },
@@ -18,6 +21,14 @@ module Statusz
     "all commits" => Proc.new { |commit| `git log --pretty=%H #{commit}`.strip }
   }
 
+  # Write out a statusz file. This should be done at deployment time.
+  #
+  # @param [String] filename the output filename.
+  # @param [Hash] options the options for the output.
+  # @option options [String] :commit The git commit for which to to output deploy information (default: HEAD).
+  # @option options [Symbol] :format The output format (one of `:html`, `:text`, or `:json`). Default: `:html
+  # @option options [Array] :fields The fields to include in the output. Default: all fields.
+  # @option options [Hash] :extra_fields A hash of extra key/value pairs to include in the output.
   def self.write_file(filename = "./statusz.html", options = {})
     options[:commit] ||= "HEAD"
     options[:format] ||= :html
@@ -36,20 +47,90 @@ module Statusz
     end
     extra_fields.each { |field, value| results[field.to_s] = value.to_s }
 
-    case options[:format]
+    File.open(filename, "w") { |file| file.puts(render(results, options[:format])) }
+  end
+
+  # @private
+  def self.render(fields, format)
+    case format
     when :text
-      output = results.map { |name, value| "#{name}:\n#{value}" }.join("\n\n")
+      fields.map { |name, value| "#{name}:\n#{value}" }.join("\n\n")
     when :json
-      output = results.to_json
+      fields.to_json
     when :html
-      html_values = results.reduce({}) do |hash, field_and_value|
-        field, value = field_and_value
+      html_values = fields.reduce({}) do |h, (field, value)|
         pair = (field == "all commits") ? { field => value.split("\n") } : { field => CGI.escapeHTML(value) }
-        hash.merge pair
+        h.merge pair
+      end
+      ERB.new(File.read(File.join(File.dirname(__FILE__), "statusz.erb"))).result(binding)
+    end
+  end
+
+  # @private
+  def self.load_json_info(filename)
+    fields = {}
+    unless filename.nil?
+      unless File.file? filename
+        raise "No such file: #{filename}."
+      end
+      begin
+        fields = JSON.parse(File.read(filename))
+      rescue StandardError => error
+        raise "Error reading json file #{filename}: #{error.message}."
+      end
+      unless fields.is_a? Hash
+        raise "Error: malformed statusz json file: #{filename}."
       end
-      output = ERB.new(File.read(File.join(File.dirname(__FILE__), "statusz.erb"))).result(binding)
+    end
+    fields
+  end
+
+  # If you wrote out a json file at deploy time, you can use this at runtime to turn the json file into any of
+  # statusz's supported formats (html, json, text) and add additional runtime values.
+  #
+  # @param [String] filename the json statusz file written at deploy time. If `filename` is `nil`, then
+  #                          statusz will output an html file containing only the fields in `extra_fields`.
+  # @param [Symbol] format then output format (one of `:html`, `:json`, `:text`). Defaults to `:html`.
+  # @param [Hash] extra_fields the extra key/value pairs to include in the output.
+  def self.render_from_json(filename = "./statusz.json", format = :html, extra_fields = {})
+    raise "Bad format: #{format}" unless [:html, :text, :json].include? format
+    fields = load_json_info(filename)
+    fields.merge! extra_fields
+    render(fields, format)
+  end
+
+  # A Rack server that can serve statusz.
+  class Server
+    # Set up the Statusz::Server Rack app.
+    #
+    # @param [String] filename the json statusz file written at deploy time. If `filename` is `nil`, then
+    #                          statusz will output an html file containing only the fields in `extra_fields`.
+    # @param [Hash] extra_fields extra key/value pairs to include in the output.
+    def initialize(filename = "./statusz.json", extra_fields = {})
+      @filename = filename
+      @extra_fields = extra_fields
     end
 
-    File.open(filename, "w") { |file| file.puts output }
+    # The usual Rack app call method.
+    def call(env)
+      headers = {}
+      path = Rack::Request.new(env).path
+      if path =~ /\.json$/
+        headers["Content-Type"] = "application/json"
+        format = :json
+      elsif path =~ /\.txt$/
+        headers["Content-Type"] = "text/plain"
+        format = :text
+      else
+        headers["Content-Type"] = "text/html"
+        format = :html
+      end
+      begin
+        body = Statusz.render_from_json(@filename, format, @extra_fields)
+      rescue StandardError => error
+        return [500, { "Content-Type" => "text/plain" }, ["Error with statusz:\n#{error.message}"]]
+      end
+      [200, headers, [body]]
+    end
   end
 end

data/lib/statusz/version.rb

@@ -1,3 +1,3 @@
 module Statusz
-  VERSION = "0.0.4"
+  VERSION = "0.1.0.pre"
 end

data/rack_example/Gemfile

@@ -0,0 +1,4 @@
+source :rubygems
+
+gem "sinatra"
+gem "thin"

data/rack_example/Gemfile.lock

@@ -0,0 +1,24 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    daemons (1.1.4)
+    eventmachine (0.12.10)
+    rack (1.4.1)
+    rack-protection (1.2.0)
+      rack
+    sinatra (1.3.3)
+      rack (~> 1.3, >= 1.3.6)
+      rack-protection (~> 1.2)
+      tilt (~> 1.3, >= 1.3.3)
+    thin (1.3.1)
+      daemons (>= 1.0.9)
+      eventmachine (>= 0.12.6)
+      rack (>= 1.0.0)
+    tilt (1.3.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  sinatra
+  thin

data/rack_example/README.md

@@ -0,0 +1,12 @@
+A simple example of using the `Statusz::Server` rack app to serve statusz.
+
+To run:
+
+    $ bundle install
+    $ bundle exec rackup
+
+Then visit a few urls:
+
+* [http://localhost:9292/statusz.html](http://localhost:9292/statusz.html)
+* [http://localhost:9292/statusz.json](http://localhost:9292/statusz.json)
+* [http://localhost:9292/statusz.txt](http://localhost:9292/statusz.txt)

data/rack_example/config.ru

@@ -0,0 +1,13 @@
+require "rack/builder"
+
+# Use the local version of statusz. In your app, you would just 'require "statusz"'.
+$:.unshift File.join(File.dirname(__FILE__), "../lib")
+require "statusz"
+
+app = Rack::Builder.new do
+  map "/" do
+    run Statusz::Server.new
+  end
+end
+
+run app

data/rack_example/generate_statusz_json.rb

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+# This script imitates the code that would live in a deploy. It generates the statusz.json file that is used
+# by the server.
+
+# Use the local version of statusz. In your app, you would just 'require "statusz"'.
+$:.unshift File.join(File.dirname(__FILE__), "../lib")
+require "statusz"
+
+Statusz.write_file "./statusz.json", :format => :json

data/rack_example/statusz.json

@@ -0,0 +1 @@
+{"git directory":"statusz","latest commit":"2ce6199c7502d18105512d048eb01b550e72f734","containing branches":"master","date":"2012-10-23 11:51:07 -0700","current user on deploy host":"caleb","git user info":"Caleb Spare <caleb@ooyala.com>","all commits":"2ce6199c7502d18105512d048eb01b550e72f734\n14cf085f9ebb64e661b78c68a5d17e758aa15147\n0b43212a1ba8727cfdc969ef9221526cd3e161ea\n5424998dd84dd952a98456b47edcd92910dd2d10\n8c370aa8e0c75377a3076f49acb0091867940e31\n20b09ce2a7dc3815a89b5b2a62f51a4a5d1b5ec6\na45ba55442b8f255a0dec124c5a14be8c4e87205\n7dae9155b2ded641d7c766a34240e9243d2c8ca6\n16bbab8ce8cccb0c9287ae0777400216e21f0c96\n3acdd8e33d319083f77e7e8838cda9578b76b00a\nccc8a28ff66c658fe52350b8c03e6a82010e64cf\n3ac95f0ad62ea05d8e378e0a1287f0c8d5cc58ff\n12c78bb369af9d4e468e0c17df2aa8d354a7e45e\n9e4baa9d354b43e11fa5919db9801a2fbb15cec4\nb97091a3f59136b539846728a65d691986e6e54f\nf27d782a6a1bc0d2e8b5b9e2bf3e9eddb5d04cf6\n18fec163be18bb7ba13ebea269d44c35f3e1ea9c\n1e4a55212cf966e03442ab5da3fb72686eee7a22\na85c9b89bf642601ea8138dee978f6ea8302b4bf\nc8e543b9d434971d8cecdf577873a303bf6fb464\n96831b4a27b3c471c3d251406cffa62c552f2dc5\nd389dc833162d09e66220ac47fabf441ca61f45e\n896fe2c83240c8493acc4a769379125307ac3d98"}

data/statusz.gemspec

@@ -14,4 +14,9 @@ Gem::Specification.new do |gem|
   gem.name          = "statusz"
   gem.require_paths = ["lib"]
   gem.version       = Statusz::VERSION
+
+  gem.add_dependency "rack"
+
+  gem.add_development_dependency "yard"
+  gem.add_development_dependency "redcarpet"
 end

metadata

@@ -1,16 +1,64 @@
 --- !ruby/object:Gem::Specification
 name: statusz
 version: !ruby/object:Gem::Version
-  version: 0.0.4
-  prerelease: 
+  version: 0.1.0.pre
+  prerelease: 6
 platform: ruby
 authors:
 - Caleb Spare
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-23 00:00:00.000000000Z
-dependencies: []
+date: 2012-10-23 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rack
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: yard
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: redcarpet
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 description: statusz is a gem that writes out git metadata at deploy time.
 email:
 - cespare@gmail.com
@@ -19,13 +67,26 @@ extensions: []
 extra_rdoc_files: []
 files:
 - .gitignore
+- .yardopts
 - Gemfile
 - LICENSE
 - README.md
 - Rakefile
+- example/Gemfile
+- example/Gemfile.lock
+- example/README.md
+- example/generate_statusz_json.rb
+- example/sample_app.rb
+- example/statusz.json
 - lib/statusz.erb
 - lib/statusz.rb
 - lib/statusz/version.rb
+- rack_example/Gemfile
+- rack_example/Gemfile.lock
+- rack_example/README.md
+- rack_example/config.ru
+- rack_example/generate_statusz_json.rb
+- rack_example/statusz.json
 - statusz.gemspec
 homepage: https://github.com/ooyala/statusz
 licenses: []
@@ -42,12 +103,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
-  - - ! '>='
+  - - ! '>'
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.10
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: statusz is a gem that writes out git metadata at deploy time.