kibana-sinatra 3.1.1.0 → 3.1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 42a24f6644365d6e9ec2c9a9fca3bf4101d88217
-  data.tar.gz: 9e00965d345f23a7299aba04689a2127ab79fd22
+  metadata.gz: be3b44aa25d39a205b25267a74ce79579c9fb6c9
+  data.tar.gz: 3d0ca8b23f8bd12767ac23006446783086ae5b21
 SHA512:
-  metadata.gz: 23127982f74f767ee8732d9a99f155785acf0624492ba76fb71d3de4c929affed233ed7ff01ad20da915947e47d422d3ec3fb595fc305df02ab0e3e660151009
-  data.tar.gz: 966859ccd8652a412a47aaf7613fb49f1ec118dfa97e7e26992a2ff1991dcc0b7b0224aefb07ac84c5bbb3d5f4fac05137e8ffaccfef2ba5a29818cd4ab21787
+  metadata.gz: 5afae95b378fbacf9386d898df649e4df07d178050ad08723bfe0db785274d0c76f7f5f4c2a1e4e98c8d991d810c4c02190366102b68e79af906760663467c38
+  data.tar.gz: c3a261f116e825ceeee673c1218655489e9f868972cb34abfd06237095343fb7dc4c2396d061f128cd26d2254e2fc8f27bc533f189cbb2914223d5a51ae23b78

data/config.ru

@@ -0,0 +1,6 @@
+require 'kibana/assets/server/lib/app'
+
+# If you need to configure elasticsearch_url, put your configuration here just like the Rails example.
+
+
+run Kibana::App

data/lib/kibana/assets/app/partials/connectionFailed.html

@@ -9,8 +9,13 @@
             <h5>Possibility #1: Your elasticsearch server is down or unreachable</h5>
             This can be caused by a network outage, or a failure of the Elasticsearch process. If you have recently run a query that required a <i>terms</i> facet to be executed it is possible the process has run out of memory and stopped. Be sure to check your Elasticsearch logs for any sign of memory pressure.
             <h5>Possibility #2: You are running Elasticsearch 1.4 or higher</h5>
-            Elasticsearch 1.4 ships with a security setting that prevents Kibana from connecting. You will need to set <i>http.cors.allow-origin</i> in your <i>elasticsearch.yml</i> to the correct protocol, hostname, and port (if not 80) that your access Kibana from. Note that if you are running Kibana in a sub-url, you should exclude the sub-url path and only include the protocol, hostname and port. For example, <i>http://mycompany.com:8080</i>, not <i>http://mycompany.com:8080/kibana</i>.
-
+            Elasticsearch 1.4 ships with a security setting that prevents Kibana from connecting. You will need to set the following in your elasticsearch.yml:
+            <p>
+              <ol>
+                <li> <i>http.cors.enabled: true</i> </li>
+                <li> <i>http.cors.allow-origin</i> to the correct protocol, hostname, and port (if not 80) that your access Kibana from. Note that if you are running Kibana in a sub-url, you should exclude the sub-url path and only include the protocol, hostname and port. For example, <i>http://mycompany.com:8080</i>, not <i>http://mycompany.com:8080/kibana</i>.</li>
+              </ol>
+            </p>
             <h5>Click back, or the home button, when you have resolved the connection issue</h5>
           </ol>
         </div>

data/lib/kibana/sinatra/version.rb

@@ -1,5 +1,5 @@
 module Kibana
   module Sinatra
-    VERSION = "3.1.1.0"
+    VERSION = "3.1.2.0"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: kibana-sinatra
 version: !ruby/object:Gem::Version
-  version: 3.1.1.0
+  version: 3.1.2.0
 platform: ruby
 authors:
 - Ian Neubert
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-10-02 00:00:00.000000000 Z
+date: 2014-11-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -122,6 +122,7 @@ files:
 - LICENSE.txt
 - README.md
 - Rakefile
+- config.ru
 - kibana-sinatra.gemspec
 - lib/kibana/assets/app/app.js
 - lib/kibana/assets/app/components/extend-jquery.js