straight-server 0.1.2 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 34f009b0de8ffbad5c9cfb46cb3044cc69b61a65
-  data.tar.gz: cf3543fde03d50bdf382957f347638ec83193497
+  metadata.gz: f8610bd49c87e428c82c658ecdc0a1f0e2299bfb
+  data.tar.gz: e046d7b179cafead65d803e4fb30e52d11a8bc11
 SHA512:
-  metadata.gz: 5cc71b6d8ffd1fdd6b727db40a9a6c12687013119712b569c89ff39fdddf35f0420ed3617f0fc066de909f8bbb5fba77bba0040f4230dd6c7959f6488a8f4c4d
-  data.tar.gz: 043c4bae520c57ac0b9e3fa96ec212ab58dbe4affe83f85a85c5f3798810681857ec8e48a78094904c6d2d9ffcd6fe6278ae6c60fc63846ab0a941668616aea6
+  metadata.gz: 0fda4cd1ecb67821380631da86fd6c2d4864c57ed5f0200b1b6d45508190a07b06e8c66e5e72a1b501df477b8da6c7f385ad4c7b059d50c51ce1f1176e570ef8
+  data.tar.gz: edb15d2d84f5de98901a3d0d3e18f7a2fb5279c6a9ed19418c9c8b400a9e6b006a3cf5b9d9d42cbcd82a7ae32861a32644048e2e0e851f32a0c09a5d71b79bae

data/.travis.yml

@@ -0,0 +1,8 @@
+gemfile: Gemfile.travis
+language: ruby
+rvm:
+  - 2.1.0
+services:
+  - redis-server
+notifications:
+  slack: straight-payments:ovM1xPrG9BmKTHGkM0k42gkP

data/Gemfile

@@ -5,8 +5,9 @@ gem "satoshi-unit"
 gem "goliath"
 gem "faye-websocket"
 gem "sequel"
-gem "logmaster", '0.1.2'
+gem "logmaster", '0.1.5'
 gem "ruby-hmac"
+gem "httparty"
 
 # Add dependencies to develop your gem here.
 # Include everything needed to run rake, tests, features, etc.
@@ -21,4 +22,5 @@ group :test do
   gem 'factory_girl'
   gem 'sqlite3'
   gem 'hashie'
+  gem 'redis'
 end

data/Gemfile.lock

@@ -1,34 +1,34 @@
 GEM
   remote: http://rubygems.org/
   specs:
-    activesupport (4.1.6)
-      i18n (~> 0.6, >= 0.6.9)
+    activesupport (4.2.1)
+      i18n (~> 0.7)
       json (~> 1.7, >= 1.7.7)
       minitest (~> 5.1)
-      thread_safe (~> 0.1)
+      thread_safe (~> 0.3, >= 0.3.4)
       tzinfo (~> 1.1)
-    addressable (2.3.6)
+    addressable (2.3.8)
     async-rack (0.5.1)
       rack (~> 1.1)
     builder (3.2.2)
     descendants_tracker (0.0.4)
       thread_safe (~> 0.3, >= 0.3.1)
     diff-lcs (1.2.5)
-    em-synchrony (1.0.3)
+    em-synchrony (1.0.4)
       eventmachine (>= 1.0.0.beta.1)
     em-websocket (0.3.8)
       addressable (>= 2.1.1)
       eventmachine (>= 0.12.9)
-    eventmachine (1.0.3)
-    factory_girl (4.4.0)
+    eventmachine (1.0.7)
+    factory_girl (4.5.0)
       activesupport (>= 3.0.0)
-    faraday (0.9.0)
+    faraday (0.9.1)
       multipart-post (>= 1.2, < 3)
-    faye-websocket (0.7.4)
+    faye-websocket (0.9.2)
       eventmachine (>= 0.12.0)
-      websocket-driver (>= 0.3.1)
-    ffi (1.9.3)
-    git (1.2.8)
+      websocket-driver (>= 0.5.1)
+    ffi (1.9.8)
+    git (1.2.9.1)
     github_api (0.11.3)
       addressable (~> 2.3)
       descendants_tracker (~> 0.0.1)
@@ -48,10 +48,13 @@ GEM
       rack (>= 1.2.2)
       rack-contrib
       rack-respond_to
-    hashie (3.3.1)
-    highline (1.6.21)
+    hashie (3.4.1)
+    highline (1.7.2)
     http_parser.rb (0.6.0)
-    i18n (0.6.11)
+    httparty (0.13.3)
+      json (~> 1.8)
+      multi_xml (>= 0.5.2)
+    i18n (0.7.0)
     jeweler (2.0.1)
       builder
       bundler (>= 1.0)
@@ -61,23 +64,23 @@ GEM
       nokogiri (>= 1.5.10)
       rake
       rdoc
-    json (1.8.1)
-    jwt (1.0.0)
+    json (1.8.2)
+    jwt (1.4.1)
     log4r (1.1.10)
-    logmaster (0.1.2)
+    logmaster (0.1.5)
       pony
     mail (2.6.3)
       mime-types (>= 1.16, < 3)
-    mime-types (2.4.3)
-    mini_portile (0.6.0)
-    minitest (5.4.1)
-    money-tree (0.8.7)
+    mime-types (2.5)
+    mini_portile (0.6.2)
+    minitest (5.6.1)
+    money-tree (0.8.9)
       ffi
-    multi_json (1.10.1)
+    multi_json (1.11.0)
     multi_xml (0.5.5)
     multipart-post (2.0.0)
-    nokogiri (1.6.3.1)
-      mini_portile (= 0.6.0)
+    nokogiri (1.6.6.2)
+      mini_portile (~> 0.6.0)
     oauth2 (1.0.0)
       faraday (>= 0.8, < 0.10)
       jwt (~> 1.0)
@@ -86,37 +89,42 @@ GEM
       rack (~> 1.2)
     pony (1.11)
       mail (>= 2.0)
-    rack (1.5.2)
+    rack (1.6.0)
     rack-accept-media-types (0.9)
-    rack-contrib (1.1.0)
+    rack-contrib (1.2.0)
       rack (>= 0.9.1)
     rack-respond_to (0.9.8)
       rack-accept-media-types (>= 0.6)
-    rake (10.3.2)
-    rdoc (4.1.2)
-      json (~> 1.4)
-    rspec (3.1.0)
-      rspec-core (~> 3.1.0)
-      rspec-expectations (~> 3.1.0)
-      rspec-mocks (~> 3.1.0)
-    rspec-core (3.1.2)
-      rspec-support (~> 3.1.0)
-    rspec-expectations (3.1.0)
+    rake (10.4.2)
+    rdoc (4.2.0)
+    redis (3.2.1)
+    rspec (3.2.0)
+      rspec-core (~> 3.2.0)
+      rspec-expectations (~> 3.2.0)
+      rspec-mocks (~> 3.2.0)
+    rspec-core (3.2.3)
+      rspec-support (~> 3.2.0)
+    rspec-expectations (3.2.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.2.0)
+    rspec-mocks (3.2.1)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.1.0)
-    rspec-mocks (3.1.0)
-      rspec-support (~> 3.1.0)
-    rspec-support (3.1.0)
+      rspec-support (~> 3.2.0)
+    rspec-support (3.2.2)
     ruby-hmac (0.4.0)
-    satoshi-unit (0.1.6)
-    sequel (4.13.0)
-    sqlite3 (1.3.9)
+    satoshi-unit (0.1.7)
+    sequel (4.22.0)
+    sqlite3 (1.3.10)
     straight (0.1.0)
+      httparty
       money-tree
-    thread_safe (0.3.4)
+      satoshi-unit
+    thread_safe (0.3.5)
     tzinfo (1.2.2)
       thread_safe (~> 0.1)
-    websocket-driver (0.3.4)
+    websocket-driver (0.5.4)
+      websocket-extensions (>= 0.1.0)
+    websocket-extensions (0.1.2)
 
 PLATFORMS
   ruby
@@ -128,8 +136,10 @@ DEPENDENCIES
   github_api (= 0.11.3)
   goliath
   hashie
+  httparty
   jeweler (~> 2.0.1)
-  logmaster (= 0.1.2)
+  logmaster (= 0.1.5)
+  redis
   rspec
   ruby-hmac
   satoshi-unit

data/Gemfile.travis

@@ -0,0 +1,26 @@
+source "http://rubygems.org"
+
+gem "straight", git: "https://github.com/snitko/straight.git"
+gem "satoshi-unit"
+gem "goliath"
+gem "faye-websocket"
+gem "sequel"
+gem "logmaster", '0.1.5'
+gem "ruby-hmac"
+gem "httparty"
+
+# Add dependencies to develop your gem here.
+# Include everything needed to run rake, tests, features, etc.
+group :development do
+  gem "bundler", "~> 1.0"
+  gem "jeweler", "~> 2.0.1"
+  gem "github_api", "0.11.3"
+end
+
+group :test do
+  gem 'rspec'
+  gem 'factory_girl'
+  gem 'sqlite3'
+  gem 'hashie'
+  gem 'redis'
+end

data/README.md

@@ -1,9 +1,16 @@
 Straight server
 ===============
-> A stand-alone Bitcoin payment gateway server
+> A stand-alone Bitcoin payment gateway server.
 > Receives bitcoin payments directly into your wallet, holds no private keys
+>
+> It is used as a backend for the hosted service http://gear.mycelium.com
+> Instead of installing the gateway yourself, you can just use
+> Mycelium Gear and accept payments through it. Of course, straight
+> into your wallet again - no private key required.
 
-> Website: http://straight.romansnitko.com
+> Website: http://gear.mycelium.com
+
+[![Build Status](https://travis-ci.org/snitko/straight-server.svg)](https://travis-ci.org/snitko/straight-server)
 
 If you'd like to accept Bitcoin payments on your website automatically, but you're not
 fond of services like Coinbase or Bitpay, which hold your bitcoins for you and require a ton
@@ -95,6 +102,22 @@ You can also subscribe to the order status changes using websockets at:
 
 It will send a message to the client upon the status change and close connection afterwards.
 
+**Order expiration**
+means that after a certain time has passed, it is no longer possible to pay for it. Each order holds
+its creation time in `#created_at` field. In turn, each order's gateway has a field called
+`#orders_expiration_period` (you can set it as an option in config file for each particular gateway or in the DB,
+depending on what approach to storing gateways you use). After this time has passed, straight-server stops
+checking whether new transactions appear on the order's bitcoin address and also changes order's status to 5 (expired).
+
+Implications of restarting the server
+-------------------------------------
+
+If you shut the server down and then start it again, all unresolved orders (status < 2 and non-expired)
+are automatically picked up and the server starts checking on them again until they expire. Please note
+that you'd need to make sure your client side reconnects to the order's websocket again. This is because
+on server shutdown, all websocket connections are closed, therefore, there's no way to automatically restore them.
+It is thus client's responsibility to check when websocket is closed, then periodically try to connect to it again.
+
 Client Example
 --------------
 I've implemented a small client example app written purely in Dart. It creates new orders,
@@ -120,7 +143,8 @@ To create an order for the new gateway, simply send this request:
 Notice that the gateway id has changed to 2. Gateway ids are assigned according to the order in
 which they follow in the config file.
 
-** Gateways from DB **
+Gateways from DB
+----------------
 When you have too many gateways, it is unwise to keep them in the config file. In that case,
 you can store gateway settings in the DB. To do that, change `~/.straight/config.yml` setting
 'gateways_source: config` to `gateways_source: db`.
@@ -131,8 +155,8 @@ there is no standard way to manage gateways through a web interface. In the futu
 In general, it shouldn't be difficult, and may look like this:
 
     $ straight-console
-
-    > g = Gateway.new
+    
+    > gateway = Gateway.new
     > gateway.pubkey                 = 'xpub1234'
     > gateway.confirmations_required = 0
     > gateway.order_class            = 'StraightServer::Order'
@@ -140,6 +164,25 @@ In general, it shouldn't be difficult, and may look like this:
     > gateway.save
     > exit
 
+One important thing to remember when using DB based Gateways is that when you want to issue a request to
+create a new order, you must use `Gateway#hashed_id` instead of `#id`. This is because otherwise it becomes very easy
+for a third-party to just go through gateways consecutively.
+
+For example, suppose you have a DB based gateway with id 23. The incorrect request to create a new order would be
+
+    POST /gateways/23/orders?amount=1 # THIS IS WRONG!
+
+We first need to find that gateway's hashed id:
+
+    $ straight-console
+    
+    > gateway = Gateway[23]
+    > gateway.hashed_id # => '587bb9b74e37f526eac47081ad61998726673760c77415d52a95bf38fba9cbe9'
+
+And then we can make a correct request:
+
+    POST /gateways/587bb9b74e37f526eac47081ad61998726673760c77415d52a95bf38fba9cbe9/orders?amount=1
+
 Using signatures
 ----------------
 If you are running straight-server on a machine separate from your online stores, you
@@ -152,38 +195,32 @@ Go to your `~/.straight/config.yml` directory and set two options for each of yo
     check_signature: true
 
 This will force gateways to check signatures when you try to create a new order. A signature is
-a HMAC SHA1 hash of the secret and an order id. Because you need order id, it means you have
+a HMAC SHA256 hash of the secret and an order id. Because you need order id, it means you have
 to actually provide it manually in the params. It can be any integer > 0, but it's better
 that it is a consecutive integer, so keep track of order ids in your application. Obviously,
 if an order with such an id already exists, the request will be rejected. A possible request
 (assuming secret is the line mentioned above in the sample config) would look like this:
 
-    POST /gateways/1/orders?amount=1&order_id=1&signature=fb0e8d863621a3e6e2bf4e81f8ab70737190d92b
+    POST /gateways/1/orders?amount=1&order_id=1&signature=aa14c26b2ae892a8719b0c2c57f162b967bfbfbdcc38d8883714a0680cf20467
 
 An example of obtaining such signature in Ruby:
 
-    require 'hmac'
-    require 'hmac-sha1'
+    require 'openssl'
     
     secret = 'a long string of random chars'
-    h = HMAC::SHA1.new(secret)
-    h << '1' # order id
-    h.hexdigest
+    OpenSSL::HMAC.digest('sha256', secret, "1").unpack("H*").first # "1" may be order_id here
 
 Straight server will also sign the callback url request. However, since the signature may be
 known to an attacker once it was used for creating a new order, we can no longer use it directly.
 Thus, Straight server will use a double signature calculated like this:
 
     secret = 'a long string of random chars'
-    h = HMAC::SHA1.new(secret)
-    h << '1' # order id
-    h2 = HMAC::SHA1.new(secret)
-    h2 << h.hexdigest
-    h2.hexdigest
+    h1 = OpenSSL::HMAC.digest('sha256', secret, "1").unpack("H*").first
+    h2 = OpenSSL::HMAC.digest('sha256', secret, h1).unpack("H*").first
 
 and then send the request to the callback url with that signature:
 
-    GET http://mystore.com/payment-callback?order_id=1&amount=1&status=2&address=1NZov2nm6gRCGW6r4q1qHtxXurrWNpPr1q&tid=tid1&data=some+random+data?signature=a61381c87ea3f7e6958ef779b6a9789ec966c2b9
+    GET http://mystore.com/payment-callback?order_id=1&amount=1&status=2&address=1NZov2nm6gRCGW6r4q1qHtxXurrWNpPr1q&tid=tid1&data=some+random+data?signature=aa14c26b2ae892a8719b0c2c57f162b967bfbfbdcc38d8883714a0680cf20467
 
 It is now up to your application to calculate that signature, compare it and
 make sure that only one such request is allowed (that is, if signature was used, it cannot be used again).
@@ -192,9 +229,40 @@ Querying the blockchain
 -----------------------
 Straight currently uses third-party services, such as Blokchain.info and Helloblock.io to track
 addresses and fetch transaction info. This means, you don't need to install bitcoind and store
-the whole blockchain on your server. If one service is down, it will automatically switch to another one. I will be adding more adapters in the future. It will also be possible to implement a cross check where if one service is lying about a transaction, I can check with another. In the future, I will add bitcoind support too for those who do not trust third-party services.
+the whole blockchain on your server. If one service is down, it will automatically switch to another one.
+I will be adding more adapters in the future. It will also be possible to implement a cross check where if
+one service is lying about a transaction, I can check with another. In the future, I will add bitcoind support
+too for those who do not trust third-party services.
+
+To sum it up, there is nothing in the architecture of this software that says you should rely on third party services
+to query the blockchain.
+
+Counting orders
+---------------
+For easy statistics and reports, it is desirable to know how many orders of each particular status each gateway has.
+For that reason optional order counters are implemented. To enable order counters, you must first install manually *redis-server*
+and then *redis* rubygem.
+
+Then edit your config file and make sure the following options are set:
 
-To sum it up, there is nothing in the architecture of this software that says you should rely on third party services to query the blockchain.
+    environment: development # name your environment here
+    count_orders: true       # enable order counting feature
+
+    redis:
+      host: localhost
+      port: 6379
+      db:       null # change to 1, 2, 3 etc. or leave as is
+      password: null # if no password is needed, leave as is
+
+After restarting the server, you can use `Gateway#order_counters` method which will
+return a hash of all the counters. Here's an example output:
+
+    { new: 132, unconfirmed: 0, paid: 34, underpaid: 1, overpaid: 2, expired: 55 }
+
+The default behaviour is to cache the output, so if you want fresh values, use `reload: true`
+option on this method:
+
+    Gateway#order_counters(reload: true)
 
 Running in production
 ---------------------
@@ -212,6 +280,93 @@ turn on email notifications, so that when a FATAL errors occurs, an email is sen
 
 I would also recommend you to use something like *monit* daemon to monitor a *straight-server* process.
 
+Running in different environments
+---------------------------------
+Additionally, there is a `--config-dir` (short version is `-c`) option that allows you to set the
+config directory for the server. It becomes quite convenient if you decide to run, for example, both
+production and staging instances on one machine. I decided against having config file sections for each environment
+as this would be more complicated and quite unnatural. Apart from different config files, one might argue you can have
+a different set of addons and different versions of them in the `~/.straight/addons` dir. So it's better to keep them separate.
+
+If you think of wrong examples out there, consider Rails: why would I want to have a database.yml file with both
+development and production sections if I know for sure I'm only running this instance in production env?
+
+So, with straight, you can simply create a separate config dir for each instance. For example, if I want to run
+both production and staging on my server, I'd do this:
+
+1. Create `~/.straight/production` and `~/.straight/staging` dirs
+2. Run two instances like this:
+
+       straight-server --config-dir=~/.straight/production 
+       straight-server --config-dir=~/.straight/staging
+
+It's worth saying that currently, there is no default settings for production, staging or development.
+It is you who defines what a production or a staging environment is, by changing the config file. Those words
+are only used as examples. You may call your environment whatever you like.
+
+However, environment name is currently used as a prefix for gateway order counters Redis entries
+(see the respective README section). You can set the current environment name using a config file option, for example:
+
+    environment: development
+
+Addons
+------
+WARNING: this is currently work in progress. The final specification of how addons should be added
+and how they interact with the server may change.
+
+Currently there is only one use case for addons and thus only one way in which addons can interact with the server itself:
+adding controllers and routes for them. Now let's look at how we should do that:
+
+1. All addons are placed under `~/.straight/addons/` (of course, it is wise to use symlinks).
+
+2. `./straight/addons.yml` file lists addons and tells straight-server what are the names of the files to be loaded.
+The format of the file is the following:
+
+    my_addon                             # <- name doesn't affect anything, just shows up in the log file
+      path: addons/my_addon/lib/my_addon # <- This is unnecessary if addon is already in the LOAD_PATH
+      module: MyAddon                    # <- actual module should be a submodule of StraightServer::Addon
+
+3. In `./straight/addons/my_addon/lib/` we will place two files, `my_addon.rb` and 'my_controller.rb'. Below is their contents:
+
+
+    # my_addon.rb
+    
+    require_relative 'my_controller'
+
+    module StraightServer
+      module Addon
+        module MyAddon
+          
+          def self.extended(obj)
+            obj.add_route /\A\/my_controller/.*\Z/ do |env|
+              controller = MyController.new(env)
+              controller.show
+            end
+          end
+
+        end
+      end
+    end
+
+As you can guess, `#add_route` is a straight-server's special method for defining routes, very similar to Rails.
+The piece of code above will force all requests where urls are starting with `/my_controller` to be handled by
+`MyController#show`:
+
+
+    # my_controller.rb
+
+    module StraightServer
+      class MyController
+        def show
+          [200, {}, "Hello world! This is MyController speaking!"]
+        end
+      end
+    end
+
+And this in turn will render us the text "Hello world! This is MyController speaking!".
+Here, we've just created our first addon.
+
+
 Requirements
 ------------
 Ruby 2.1 or later.
@@ -220,8 +375,6 @@ Donations
 ---------
 To go on with this project and make it truly awesome, I need more time. I can only buy free time with money, so any donation is highly appreciated. Please send bitcoins over to **1D3PknG4Lw1gFuJ9SYenA7pboF9gtXtdcD**
 
-There are [development plans](http://straight.romansnitko.com/#todo) for this software you might be interested in.
-
 Credits
 -------
 Author: [Roman Snitko](http://romansnitko.com)

data/Rakefile

@@ -25,3 +25,10 @@ Jeweler::Tasks.new do |gem|
 end
 Jeweler::RubygemsDotOrgTasks.new
 
+begin
+  require 'rspec/core/rake_task'
+  RSpec::Core::RakeTask.new(:spec)
+  task default: :spec
+rescue LoadError
+  # no rspec available
+end

data/VERSION

@@ -1 +1 @@
-0.1.2
+0.2.0

data/benchmark/addons.yml

@@ -0,0 +1,15 @@
+# This is where you put info about your addons.
+#
+# Addons are just modules that extend the StraightServer::Server module.
+# 
+# Addon modules can be both rubygems or files under ~/.straight/addons/.
+# If ~/.straight/addons.yml contains a 'path' key for a particular addon, then it means
+# the addon is placed under the ~/.straight/addons/. If not, it is assumed it is
+# already in the LOAD_PATH somehow, with rubygems for example.
+#
+#
+# Example:
+#
+#   payment_ui:               # <- name doesn't affect anything, just shows up in the log file
+#     path: addons/payment_ui # <- This is unnecessary if addon is already in the LOAD_PATH
+#     module: PaymentUI       # <- actual module should be a submodule of StraightServer::Addon

data/benchmark/config.yml

@@ -0,0 +1,78 @@
+# If set to db, then use DB table to store gateways,
+# useful when your run many gateways on the same server.
+gateways_source: config
+
+environment: development
+
+# This enabled order counting using Redis. Please see he README file for details.
+# You're gonna need to install redis-server and redis rubygem on your system and provide
+# redis-server connection details below.
+count_orders: false
+
+# Uncomment this if you want to use Gateway's order counters feature
+# It requires redis.
+#redis:
+  #host: localhost
+  #port: 6380
+  #db:       null # change to 1, 2, 3 etc. or leave as is
+  #password: null # if no password is needed, leave as is
+
+gateways:
+  default:
+    pubkey: xpub6AHA9hZDN11k2ijHMeS5QqHx2KP9aMBRhTDqANMnwVtdyw2TDYRmF8PjpvwUFcL1Et8Hj59S3gTSMcUQ5gAqTz3Wd8EsMTmF3DChhqPQBnU
+    confirmations_required: 0
+    order_class: "StraightServer::Order"
+    secret: 'secret'
+    check_signature: false
+    callback_url: 'http://localhost:3000/my_app/payment_callback'
+    default_currency: 'BTC'
+    orders_expiration_period: 600 # seconds
+
+    # This options decides whether we should also check the DB for status updates first
+    # when we check order status. That is, if we're tracking an order and this option
+    # is set to true, it first fetches the fields from the local DB, sees if the status has changed there,
+    # and if it did - we no longer need to query the blockchain.
+    #
+    # Usecase? Currently mostly debugging (so set it to false for production). For example,
+    # when testing payments, you don't actually want to pay, you can just run the server console,
+    # change order status in the DB and see how your client picks it up, showing you that your
+    # order has been paid for.
+    check_order_status_in_db_first: true # Consider changing to `false` in production.
+
+    # The order matters here, we check for prices with the first adapter,
+    # if it fails, move on to the next
+    exchange_rate_adapters:
+      - Bitpay
+      - Coinbase
+      - Bitstamp
+
+    # This affects whether it is possible to create a new order with the gateway.
+    # If it's set to false, then it won't be possible to create a new order, but
+    # it will keep checking on the existing ones.
+    active: true
+
+logmaster:
+  log_level: INFO # Wise to change to WARN for production
+  file: straight.log
+  raise_exception: false 
+  name: Straight server logger
+
+  # These options bellow send you email whenever a FATAL error occurs.
+  # You probably want to uncomment them for production. See https://github.com/snitko/logmaste
+  # for various email options.
+  #
+  #email_config:
+    #to: 'me@email.foo'
+    #from: "logmaster@yourapp.com"
+
+db:
+  adapter: sqlite
+  name: straight.db # file is always located in ~/.straight
+
+  # No need to set these options for sqlite,
+  # but other DBs may require them.
+  #
+  #user: username
+  #password: password
+  #host: hostname
+  #port: 1234

data/benchmark/default_last_keychain_id

@@ -0,0 +1 @@
+1520

data/benchmark/server_secret

@@ -0,0 +1 @@
+fyjoq0s7c07l7iwk

data/bin/goliath.log

@@ -0,0 +1,6 @@
+[10084:INFO] 2015-04-16 04:12:10 :: Starting server on 0.0.0.0:9696 in development mode. Watch out for stones.
+[10084:INFO] 2015-04-16 04:12:21 :: Status: 200, Content-Length: 963, Response Time: 24.10ms
+[10084:INFO] 2015-04-16 04:12:21 :: Status: 200, Content-Length: 366, Response Time: 3.11ms
+[10084:INFO] 2015-04-16 04:12:26 :: Status: 200, Content-Length: 963, Response Time: 2.73ms
+[10084:INFO] 2015-04-16 04:12:26 :: Status: 200, Content-Length: 366, Response Time: 3.25ms
+[10084:INFO] 2015-04-16 04:12:40 :: Status: 500, Content-Length: 99, Response Time: 3.67ms