rvnstat 1.0.4

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: c9cf2701027ba4e7f0239a849ceb24d47240c8b8
+  data.tar.gz: ca96d754fde08f1d0c7f53784a6efa8eef5e2834
+SHA512:
+  metadata.gz: 790e2547931e84c1c868440f0f088d594d1d3d5e575f46b35e7799e27d8c444e5f556962675d323deadb965d1901b3d0f32104ab3bb64e45ce7f2a8e917e8c24
+  data.tar.gz: f8398c3c4d86863d00972c3835a19b70390bba015fd829aebd5c50bd3df0d736fc34baa8ea8a1da77927c1aace59d7dbba354aaf36916ee43b125c8e732ef9de

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,6 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in rvnstat.gemspec
+gem 'groupdate'
+gem 'filesize'
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2014 TODO: Write your name
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,34 @@
+# Rvnstat
+
+Ruby + Sinatra + Bootstrap + Highcharts + vnstat = awesome sauce!
+
+## Requirements
+ - vnstat
+ - sinatra
+ - vidibus-sysinfo
+ - filesize
+ - sinatra
+ 
+## Installation
+gem install rvnstat or clone this repo for running with passenger.
+
+## Usage
+
+You can run it via nginx/apache with passenger or with rackup.
+
+ - Add your path to vnstat, port and the interface you want to pull data from in the rvnstat.yml file.
+ - Place your rvnstat.yml in the folder where you run the binary:
+ 	- Run 'rvnstat' to start 	
+ - Access it via http://IP:port
+ 
+ ## Screen Shot
+ 
+ ![Alt text](ss.png "Screen Shot")
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/bin/rvnstat

@@ -0,0 +1,9 @@
+#!/usr/bin/env ruby
+require 'require.rb'
+project_root = ENV['GEM_HOME']+"/gems/rvnstat"
+Dir.glob(project_root + '/views/*', &method(:require))
+
+Rack::Handler::WEBrick.run(
+      App.new,
+      :Port => Rconfig.port
+  )

data/config.ru

@@ -0,0 +1,4 @@
+require './lib/app'
+
+
+run App.new

data/config.yml

@@ -0,0 +1,3 @@
+vnstat_path: /usr/bin/vnstat
+interface: eth0
+port: 9000

data/lib/app.rb

@@ -0,0 +1,102 @@
+#!/usr/bin/env ruby
+require "require.rb"
+
+set :views, './views'
+set :public_dir, './public'
+
+class App < Sinatra::Application
+
+  set :static, true                             # set up static file routing
+  set :public, ENV['GEM_HOME']+'/gems/rvnstat-1.0.4/public'
+  
+  set :views,  ENV['GEM_HOME']+'/gems/rvnstat-1.0.4/views'
+  
+ get '/' do
+  erb :index
+ end
+
+get '/live_traffic' do
+  erb :live_traffic, :layout => false
+ end
+
+get '/live' do
+    newVnstat = Vnstat.new
+    @x = newVnstat.live_traffic
+    content_type :json
+    results = []
+    time = Time.now.to_i * 1000
+    json = results.push(time,@x).to_json
+end
+
+ get '/day_detail' do
+ 	newVnstat = Vnstat.new
+ 	x = newVnstat.run(Rconfig.vnstat_path,Rconfig.interface)
+ 	y = x[:day]
+ 	@dates = []
+ 	@rx = []
+ 	@tx = []
+ 	y.each do |z|
+ 		z.each do |x|
+	 		@dates.push(x[:date])
+	 		@rx.push(x[:rx].to_i / 1024)
+	 		@tx.push(x[:tx].to_i / 1024)
+			end
+       	end
+       	erb :day_detail, :layout => false
+ end
+ 
+  get '/day_total' do
+ 	newVnstat = Vnstat.new
+ 	x = newVnstat.run(Rconfig.vnstat_path,Rconfig.interface)
+ 	y = x[:day]
+ 	@total = []
+ 	@dates = []
+ 	y.each do |z|
+ 		z.each do |x|
+	 		@total.push(x[:total].to_i / 1024)
+	 		@dates.push(x[:date])
+			end
+       	end
+       	erb :day_total, :layout => false
+    end
+
+  get '/top_ten' do
+  	newVnstat = Vnstat.new
+ 	x = newVnstat.run(Rconfig.vnstat_path,Rconfig.interface)
+ 	y = x[:top]
+ 	@top = []
+ 	y.each do |z|
+ 		z.each do |x|
+ 		  @top.push(:date => x[:date],:rx => x[:rx],:tx => x[:tx],:total => x[:total])
+ 		end
+ 	end
+  	erb :top_ten, :layout => false
+  end
+  
+  get '/monthly' do
+    newVnstat = Vnstat.new
+  x = newVnstat.run(Rconfig.vnstat_path,Rconfig.interface)
+  y = x[:month]
+  @top = []
+  y.each do |z|
+    z.each do |x|
+      @top.push(:date => x[:date],:rx => x[:rx],:tx => x[:tx],:total => x[:total])
+    end
+  end
+    erb :monthly, :layout => false
+  end
+
+  get '/hourly' do
+    newVnstat = Vnstat.new
+  x = newVnstat.run(Rconfig.vnstat_path,Rconfig.interface)
+  y = x[:hour]
+  @hour = []
+  y.each do |z|
+    z.each do |x|
+      @hour.push(:date => x[:date],:rx => x[:krx],:tx => x[:ktx])
+    end
+  end
+    erb :hourly, :layout => false
+  end
+
+end

data/lib/config.rb

@@ -0,0 +1,13 @@
+require 'require.rb'
+require 'yaml'
+
+class Rconfig
+	config = YAML.load_file("rvnstat.yml")
+    class << self; attr_accessor :vnstat_path end
+    class << self; attr_accessor :interface end
+    class << self; attr_accessor :port	end
+    
+    @vnstat_path = config["vnstat_path"]
+    @interface = config["interface"]
+    @port = config["port"]
+  end

data/lib/require.rb

@@ -0,0 +1,10 @@
+require 'rubygems'
+require 'sinatra'
+require 'config.rb'
+require 'app.rb'
+require 'vnstat'
+require	'yaml'
+require 'date'
+require 'vidibus-sysinfo'
+require 'json'
+require 'filesize'

data/lib/rvnstat.rb

@@ -0,0 +1,5 @@
+require "rvnstat/version"
+
+module Rvnstat
+  # Your code goes here...
+end

data/lib/rvnstat/version.rb

@@ -0,0 +1,3 @@
+module Rvnstat
+  VERSION = "1.0.4"
+end

data/lib/vnstat.rb

@@ -0,0 +1,74 @@
+require 'require.rb'
+
+class Vnstat
+	#run vmstat and grab data
+def live_traffic
+	traffic = nil
+	traffic = Vidibus::Sysinfo.throughput
+	return traffic
+end
+
+def run(vnstat_path,interface)
+		v = %x[#{vnstat_path} --dumpdb -i #{interface}]
+		hash = {}
+		day = []
+		month =[]
+		hour = []
+		date = nil
+		rx = nil
+		tx = nil
+		total = nil
+		array = []
+		top = []
+		x =  v.each_line.each do |y|
+		  array.push(y)
+		end
+
+		array.each do |y|
+							if y[0] == "d"
+								x = y.split(';')
+								if x[7].chomp == '1'
+					                        date = x[2].chomp.to_i
+					                        rx = x[3].to_i
+					                        tx = x[4].to_i
+					                        total = rx + tx
+											b = [{:date => Time.at(date).strftime("%D"),:rx => Filesize.from("#{rx} MB").to_f('KB'),:tx => Filesize.from("#{tx} MB").to_f('KB'),:total => Filesize.from("#{total} MB").to_f('KB')}]
+					                        day.push(b)
+					            end
+					                      	
+					        elsif y[0] == "m"
+								x = y.split(';')
+								if x[7].chomp == '1'
+					                        date = x[2].chomp.to_i
+					                        rx = x[3].to_i
+					                        tx = x[4].to_i
+					                        total = rx + tx
+											b = [{:date => Time.at(date).strftime("%B"),:rx => Filesize.from("#{rx} MB").pretty,:tx => Filesize.from("#{tx} MB").pretty,:total => Filesize.from("#{total} MB").pretty}]					                        
+					                        month.push(b)
+					            end
+
+
+					        elsif y[0] == "h"
+					        				x = y.split(';')
+					                        date = x[2].chomp.to_i
+					                        krx = x[3].chomp
+					                        ktx = x[4].chomp
+					                        b = [{:date => Time.at(date).strftime("%D - %l%P"),:krx => Filesize.from("#{krx} KB").pretty,:ktx => Filesize.from("#{ktx} KB").pretty}]
+					                        hour.push(b)
+					        end
+	end					        	
+					        array[55...65].each do |y|
+					        	x = y.split(';')
+								if x[7].chomp == '1'
+					                        date = x[2].chomp.to_i
+					                        rx = x[3].to_i
+					                        tx = x[4].to_i
+					                        total = rx + tx
+											b = [{:date => Time.at(date).strftime("%D"),:rx => Filesize.from("#{rx} MB").pretty,:tx => Filesize.from("#{tx} MB").pretty,:total => Filesize.from("#{total} MB").pretty}]					                        
+					                        top.push(b)
+					            end
+							end
+	hash = { :day => day,:month => month, :hour => hour,:top => top}
+	return hash
+	end
+end

data/public/CNAME

@@ -0,0 +1 @@
+getbootstrap.com

data/public/CONTRIBUTING.md

@@ -0,0 +1,192 @@
+# Contributing to Bootstrap
+
+Looking to contribute something to Bootstrap? **Here's how you can help.**
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of
+the developers managing and developing this open source project. In return,
+they should reciprocate that respect in addressing your issue or assessing
+patches and features.
+
+
+## Using the issue tracker
+
+The [issue tracker](https://github.com/twbs/bootstrap/issues) is
+the preferred channel for [bug reports](#bug-reports), [features requests](#feature-requests)
+and [submitting pull requests](#pull-requests), but please respect the following
+restrictions:
+
+* Please **do not** use the issue tracker for personal support requests.  Stack
+  Overflow ([`twitter-bootstrap-3`](http://stackoverflow.com/questions/tagged/twitter-bootstrap-3) tag) or [IRC](https://github.com/twbs/bootstrap/blob/master/README.md#community) are better places to get help.
+
+* Please **do not** derail or troll issues. Keep the discussion on topic and
+  respect the opinions of others.
+
+* Please **do not** open issues or pull requests regarding the code in
+  [`Normalize`](https://github.com/necolas/normalize.css) (open them in
+  their respective repositories).
+
+
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful, so thanks!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** — try to reproduce it using the
+   latest `master` or development branch in the repository.
+
+3. **Isolate the problem** — ideally create a [reduced test
+   case](http://css-tricks.com/6263-reduced-test-cases/) and a live example.
+   [This JS Bin](http://jsbin.com/EBAwOkOK/1) is a helpful template.
+
+
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? Do other browsers show the bug differently? What
+would you expect to be the outcome? All these details will help people to fix
+any potential bugs.
+
+Example:
+
+> Short and descriptive example bug report title
+>
+> A summary of the issue and the browser/OS environment in which it occurs. If
+> suitable, include the steps required to reproduce the bug.
+>
+> 1. This is the first step
+> 2. This is the second step
+> 3. Further steps, etc.
+>
+> `<url>` - a link to the reduced test case
+>
+> Any other information you want to share that is relevant to the issue being
+> reported. This might include the lines of code that you have identified as
+> causing the bug, and potential solutions (and your opinions on their
+> merits).
+
+
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea
+fits with the scope and aims of the project. It's up to *you* to make a strong
+case to convince the project's developers of the merits of this feature. Please
+provide as much detail and context as possible.
+
+
+## Pull requests
+
+Good pull requests—patches, improvements, new features—are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any significant pull request (e.g.
+implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the
+project's developers might not want to merge into the project.
+
+Please adhere to the [coding guidelines](#code-guidelines) used throughout the
+project (indentation, accurate comments, etc.) and any other requirements
+(such as test coverage).
+
+Adhering to the following process is the best way to get your work
+included in the project:
+
+1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
+   and configure the remotes:
+
+   ```bash
+   # Clone your fork of the repo into the current directory
+   git clone https://github.com/<your-username>/bootstrap.git
+   # Navigate to the newly cloned directory
+   cd bootstrap
+   # Assign the original repo to a remote called "upstream"
+   git remote add upstream https://github.com/twbs/bootstrap.git
+   ```
+
+2. If you cloned a while ago, get the latest changes from upstream:
+
+   ```bash
+   git checkout master
+   git pull upstream master
+   ```
+
+3. Create a new topic branch (off the main project development branch) to
+   contain your feature, change, or fix:
+
+   ```bash
+   git checkout -b <topic-branch-name>
+   ```
+
+4. Commit your changes in logical chunks. Please adhere to these [git commit
+   message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+   or your code is unlikely be merged into the main project. Use Git's
+   [interactive rebase](https://help.github.com/articles/interactive-rebase)
+   feature to tidy up your commits before making them public.
+
+5. Locally merge (or rebase) the upstream development branch into your topic branch:
+
+   ```bash
+   git pull [--rebase] upstream master
+   ```
+
+6. Push your topic branch up to your fork:
+
+   ```bash
+   git push origin <topic-branch-name>
+   ```
+
+7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
+    with a clear title and description against the `master` branch.
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project owners to
+license your work under the terms of the [MIT License](LICENSE.md).
+
+
+## Code guidelines
+
+### HTML
+
+- Two spaces for indentation, never tabs.
+- Double quotes only, never single quotes.
+- Always use proper indentation.
+- Use tags and elements appropriate for an HTML5 doctype (e.g., self-closing tags).
+- Use CDNs and HTTPS for third-party JS when possible. We don't use protocol-relative URLs in this case because they break when viewing the page locally via `file://`.
+- Use [WAI-ARIA](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA) attributes in documentation examples to promote accessibility.
+
+### CSS
+
+- CSS changes must be done in `.less` files first, never just in the compiled `.css` files.
+- Adhere to the [CSS property order](http://markdotto.com/2011/11/29/css-property-order/).
+- Multiple-line approach (one property and value per line).
+- Always a space after a property's colon (e.g., `display: block;` and not `display:block;`).
+- End all lines with a semi-colon.
+- For multiple, comma-separated selectors, place each selector on its own line.
+- Attribute selectors, like `input[type="text"]` should always wrap the attribute's value in double quotes, for consistency and safety (see this [blog post on unquoted attribute values](http://mathiasbynens.be/notes/unquoted-attribute-values) that can lead to XSS attacks).
+- Attribute selectors should only be used where absolutely necessary (e.g., form controls) and should be avoided on custom components for performance and explicitness.
+- Series of classes for a component should include a base class (e.g., `.component`) and use the base class as a prefix for modifier and sub-components (e.g., `.component-lg`).
+- Avoid inheritance and over nesting—use single, explicit classes whenever possible.
+- When feasible, default color palettes should comply with [WCAG color contrast guidelines](http://www.w3.org/TR/WCAG20/#visual-audio-contrast).
+
+### JS
+
+- No semicolons
+- Comma first
+- 2 spaces (no tabs)
+- strict mode
+- "Attractive"
+
+
+## License
+
+By contributing your code, you agree to license your contribution under the [MIT license](https://github.com/twbs/bootstrap/blob/master/LICENSE).
+
+Prior to v3.1.0, Bootstrap was released under the Apache License v2.0.
+