config_server 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0be6fe32a6dfb9d57c1bd3c442df55ce38244a4f
-  data.tar.gz: 3b4b1f0d22b96bf3e827e575c8ddfd143afabcfc
+  metadata.gz: 2583c16164af166f046609b2105bc10fd59970ae
+  data.tar.gz: d82db544e9306d3524f9aec546099df1a4c9a2a3
 SHA512:
-  metadata.gz: 998cc908d8e2eb17a4524ec87ec14ed47a7e0270d34bc1afbf921e2a2130eedec491f43aa2deaecc616ce1744791962fc2f6672b597c4b226a1a0c4d46c94183
-  data.tar.gz: 10a96ca9ded60eec7d7b7ca20d1cf65ab2ed4bd99c0a72bd51db4c371649e70bfe65ef47438471bc88e2566c812e5e9afc2e4640b7fcd0e7e3645fc3270eebb1
+  metadata.gz: 5b0c0721800b09b6fe0561920c04f028ec9c999c557407430297ed2c155db35eab3ccd99702cb33bbc4b786d8c0f008c00566c2542ecd943e42b68c3f835f303
+  data.tar.gz: 38dcd62497811299e18fdac9de58caf3f0d0eb365ad4d7f0e08025a777414dcc3754ebfe9246e67aeedec877d8db4709c66084b7d75d186258e0a5d8a14572d7

data/README.md

@@ -1,25 +1,10 @@
 # ConfigServer
 
-The simplest way to store YAML configuration and serve it over HTTP
+The simplest way to serve configuration over HTTP.
+Currently support YAML files as configuration DB.
 
-## Installation
+## Example config.yml
 
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'config_server'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install config_server
-
-## Usage
-To run the server you must have a configuration file first:
 ```yaml
 #config.yml
 
@@ -37,6 +22,36 @@ staging:
   nginx:
     server_name: www.me.staging
 ```
+
+You have two options for running the server:
+
+## Option 1: Running With Docker
+
+ConfigServer has a docker image on Docker Hub. To use it create a config.yml
+file and mount it into the container:
+
+    $ docker run -d -p 8080:8080 -v /path/to/your/config.yml:/usr/src/app/config.yml nanit/config_server
+
+## Option 2: Running Your Ruby Script
+
+### 1. Install config_server Gem
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'config_server'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install config_server
+
+### 2. Run Your Ruby Script
+
 Then create the following ruby file:
 ```ruby
 #my_configuration_server.rb
@@ -46,12 +61,18 @@ require 'config_server'
 ConfigServer.start("config.yml")
 ```
 
-and run `bundle exec ruby my_configuration_server.rb`
+Then run:
+
+    $ bundle exec ruby my_configuration_server.rb
+
+## Querying The Server
 
 To get a value just chain the key path as your HTTP request path:
-`GET /production/nginx/server_name` to get the corresponding keys.
 
-## Some More Examples
+`GET /production/nginx/server_name` to get the corresponding keys in your
+config.yml file.
+
+Some examples:
 
 1. In the first example we get the production db host for the api service
 2. In the second example we ask for a non existing key and get a 404 response

data/docker/Gemfile.lock

@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    config_server (0.1.0)
+    config_server (0.1.1)
       rack
     rack (1.6.4)
 

data/lib/config_server/app.rb

@@ -14,7 +14,7 @@ class ConfigServer::App
   def call(env)
     request_path = env['PATH_INFO']
     @logger.info "Got request for #{request_path}"
-    value = get_key_from_yaml(request_path)
+    value = (request_path == "/ping" && "PONG") || get_key_from_yaml(request_path)
     if value
       ['200', {'Content-Type' => 'text/plain'}, [value]]
     else

data/lib/config_server/version.rb

@@ -1,3 +1,3 @@
 module ConfigServer
-  VERSION = "0.1.1"
+  VERSION = "0.1.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: config_server
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Erez Rabih
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2015-11-11 00:00:00.000000000 Z
+date: 2015-11-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rack