scout_realtime 1.0.3.pre → 1.0.3

data/CHANGELOG.md

@@ -1,6 +1,7 @@
-## 1.0.3.pre
+## 1.0.3
 
 * switch to relatives paths in templates, so it will work in an nginx subfolder.
+* Updating server_metrics dependency to 1.2.3
 
 ## 1.0.2
 

data/README.md

@@ -22,12 +22,12 @@ When you're done, you can stop the daemon with: `scout_realtime stop`
 Scout realtime is a better `top` command: it gives you disk, memory, network, CPU, and process metrics. And it gives you smooth-flowing charts for everything. **Troubleshooting is so much easier when you can see a few minutes worth of realtime data** instead of watching individual numbers flash on your terminal window.   
 
 
-## Questions & troubleshooting
+## Questions & Troubleshooting
 
-* **Something isn't working. Where's the log?** By default, the a log is written to `~/scout_realtime.log`
+* **Something isn't working. Where's the log?** By default, the log is written to `~/scout_realtime.log`
 * **Does my server need to have a public IP or domain name?** Yes, you need a public IP or domain name to view Scout Realtime in your browser.
 * **Installing the gem didn't work.** You need Ruby 1.8.7+ on your server to run Scout Realtime. Try `which ruby` (to confirm you have Ruby), `ruby -v` (to show Ruby's version), and `which gem` to confirm you have Ruby gems (Ruby's package manager) available.
-* **Can multiple people view the realtime stats?** Yes. You'll probably want to open a port in your firewall instead of relying in the SSH tunnel for access: `sudo iptables -A INPUT -p tcp --dport 5555 -j ACCEPT`
+* **Can multiple people view the realtime stats?** Yes. You'll probably want to open a port in your firewall instead of relying on the SSH tunnel for access: `sudo iptables -A INPUT -p tcp --dport 5555 -j ACCEPT`
 * **The SSH tunnel is a pain. Is there a way to set up persistent access?** Yes -- open a port in your firewall using the iptables command above.
   * **Is that safe?** It's as safe or safer than any any other service you have listening for HTTP traffic. The realtime web server only serves two endpoints, and there's nothing available at either of those endpoints that can be used in an attack.
 * **5555 is a strange number. Can I run it on a different port?** Yes. `scout_realtime --help` for options.

data/lib/scout_realtime/version.rb

@@ -1,5 +1,5 @@
 module Scout
   module Realtime
-    VERSION = "1.0.3.pre"
+    VERSION = "1.0.3"
   end
 end

data/scout_realtime.gemspec

@@ -26,5 +26,5 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "pry"
 
   # Runtime dependencies
-  spec.add_runtime_dependency "server_metrics", "~> 1.2.2"
+  spec.add_runtime_dependency "server_metrics", "~> 1.2.3"
 end

metadata

@@ -1,8 +1,8 @@
 --- !ruby/object:Gem::Specification
 name: scout_realtime
 version: !ruby/object:Gem::Version
-  version: 1.0.3.pre
-  prerelease: 6
+  version: 1.0.3
+  prerelease: 
 platform: ruby
 authors:
 - Andre Lewis
@@ -116,7 +116,7 @@ dependencies:
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.2.2
+        version: 1.2.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -124,7 +124,7 @@ dependencies:
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 1.2.2
+        version: 1.2.3
 description: Realtime server metrics in your browser.
 email:
 - support@scoutapp.com
@@ -711,9 +711,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
-  - - ! '>'
+  - - ! '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23
@@ -730,3 +730,4 @@ test_files:
 - test/models/processes_test.rb
 - test/runner_test.rb
 - test/test_helper.rb
+has_rdoc: