veye 0.0.2

checksums.yaml

@@ -0,0 +1,15 @@
+---
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    ZDYwMzRlOWM5ZTI0MDI5OTMyNTIzYTVjMDhmYjRlYWJhYjE0YzM3OA==
+  data.tar.gz: !binary |-
+    N2QyYWE5NmZjMzgwODg1MDlkMjNjM2Q5YjgxZWE1ZjI0OTc4YjIwOQ==
+SHA512:
+  metadata.gz: !binary |-
+    YWI3ZmZlYWY4YmY0YzY1MTUzMzUxYjkwOWY1OTllODhhZjZjYTMzOTE1MDJl
+    NDRmOWQ2NjA3OWY1N2E5YWY5NzJjY2YyOTRhNjY4YmQyMTVkYmI3MTVhZmUx
+    NDdkNmUyMGE0MGI1YjBkMTNhMmM0Njk5MDE3MTA2ODk3ODhhYTc=
+  data.tar.gz: !binary |-
+    YzZjYWVmZTIyMGU2ZjI4NGY4Y2JkNGFkZGQ1NzIzOTMyMWU2OTU5MDg4NGMy
+    NDRiNDNjYzkxNmUyYzNjZmMwM2FhMzc2ODg0ZTA3YzM0YWM5MjExMzRkMjk1
+    NTg3NWI2YTAwNjQ1YTEyYTM5YmQzZGE5ZTVlZmFlYWE2ZjM1MmM=

data/Gemfile

@@ -0,0 +1,2 @@
+source 'https://rubygems.org'
+gemspec

data/Gemfile.lock

@@ -0,0 +1,51 @@
+PATH
+  remote: .
+  specs:
+    veye (0.0.2)
+      awesome_print (= 1.2.0)
+      gli (= 2.8.0)
+      rainbow
+      rest-client (= 1.6.7)
+      terminal-table (= 1.4.5)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    aruba (0.5.1)
+      childprocess (~> 0.3.6)
+      cucumber (>= 1.1.1)
+      rspec-expectations (>= 2.7.0)
+    awesome_print (1.2.0)
+    builder (3.1.4)
+    childprocess (0.3.6)
+      ffi (~> 1.0, >= 1.0.6)
+    cucumber (1.2.1)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.11.0)
+      json (>= 1.4.6)
+    diff-lcs (1.1.3)
+    ffi (1.3.0)
+    gherkin (2.11.5)
+      json (>= 1.4.6)
+    gli (2.8.0)
+    json (1.7.6)
+    mime-types (1.25)
+    rainbow (1.1.4)
+    rake (10.0.3)
+    rdoc (3.12)
+      json (~> 1.4)
+    rest-client (1.6.7)
+      mime-types (>= 1.16)
+    rspec-expectations (2.12.1)
+      diff-lcs (~> 1.1.3)
+    terminal-table (1.4.5)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba
+  rake
+  rdoc
+  veye!

data/README.md

@@ -0,0 +1,271 @@
+# Veye
+
+[VersionEye](http://www.versioneye.com/) is a cross-platform search engine and crowdsourcing app for opensource software libraries. 
+
+ * Take advantage of the extended search to find any library you look for. 
+ * Follow and track your favorite software packages via RSS feed.
+ * Leave comments and add additional meta information to the libraries to improve the quality of the data. 
+ * Contribute to this crowdsourcing project to make the world a better place for software developers.
+
+
+**veye** is commandline tool to make all this available on command-line and manipulate results with awesome tools and scripts. 
+
+**PS:** Our _premium customers_ can also use offline search. Please send your email to `contact@versioneye.com` to get more information.
+
+Most endpoints require the api-key, which you can get [here](https://www.versioneye.com/settings/api).
+
+![Main help](http://dl.dropbox.com/u/19578784/versioneye/cli_start_page.png)
+
+
+### Install
+
+
+```
+  $> gem install veye
+```
+
+### Using dev-version
+
+###### Download source
+
+ ```bash
+  $> git clone https://github.com/versioneye/veye.git
+  $> cd veye
+ ```
+
+###### Run without installing
+ ```
+  $> bundle
+  $> bundle exec bin/veye ping
+ ```
+ 
+###### Or build Gem file and install it as global command
+
+  ```
+  $> gem build veye.gemspec
+  $> veye help
+  $> veye ping
+  ```
+ 
+### Initial configuration
+
+The tool will raise exception when a configuration file is missing. The tool needs configuration file to keep user specific settings and  authorization key. 
+
+
+  ```
+  $> veye initconfig
+  #it creates configuration file for VersionEye CLI
+  $> cat ~/.veye.rc
+  :api_key: <add your key>
+  :server: 127.0.0.1
+  :port: "3000"
+  ....
+  ```
+
+# Basic usage
+
+
+### Check service
+You can use this service to check does the tool works and tests is our API accessible. This command doesnt need authorization.
+
+ ```bash
+   $> veye ping
+   pong
+ ```
+
+### Search packages
+
+This command opens window to magnificient world of software packages - VersionEye has ~ 200K software libraries and it's reachable via your commandline.
+
+###### Get command help
+
+ ```bash
+   $> veye search help
+ ```
+ 
+###### Basic package search with language filtering
+
+ ```bash
+   $> veye search junit
+   $> veye search -l java
+   $> veye search --language java
+   $> veye search --language-name=java
+   
+   #search packages for multiple languages
+   $> veye search --lang=nodejs,php
+ ```
+
+###### Use result paging
+
+  ```
+    $> veye search junit --page 2
+    $> veye search junit --page-number=2
+    $> veye search json --lang=r,php --page=2
+    
+    #you can cancel pagination with --no-pagination argument
+    $> veye search junit --page 3 --no-pagination
+  ```
+
+###### Use different output format
+
+**pretty print** - human readable output
+ 
+```bash
+  $> veye search json --format=pretty
+```
+ 
+  ![Pretty format](https://s3-eu-west-1.amazonaws.com/veye/search_format_pretty.png)
+ 
+ **csv** - to pipeline output to [awk](http://www.gnu.org/software/gawk/manual/gawk.html)
+ 
+ ```bash
+  $> veye search json --format=csv
+ ```
+
+ ![CSV format](https://s3-eu-west-1.amazonaws.com/veye/search_format_csv.png)
+
+ **json** - for manipulating results with [jq](http://stedolan.github.com/jq/) . 
+ Check out our jq recipes in [wiki](https://github.com/versioneye/veye/wiki/jq-recipes) .
+ 
+ 
+ ```bash
+  $> veye search json --format=json
+ ```
+ 
+ ![Json format](https://s3-eu-west-1.amazonaws.com/veye/search_format_json.png)
+ 
+ **table view**
+ 
+ ```bash
+  $> veye search json --format=table
+ ```
+ ![Table output](https://s3-eu-west-1.amazonaws.com/veye/search_format_table.png)
+ 
+
+###### Empty response
+
+There will be situation, when [VersionEye](http://versioneye.com) dont have information about your search, then you will see similar response on commandline:
+
+  ```
+  No results for 'json' with given parameters: 
+  {:q=>"json", :lang=>"python", :page=>1}
+  ```
+  
+### Global options
+
+You can override your default global options by adding proper keyword and value.
+For example to override a number of port, when doing search:
+
+```
+  $> veye --port=4567 search json --lang=php,nodejs
+```
+
+### Package information
+
+Ok, thats most trickiest part of our tool. You need to prepend a language of package just before product's key. For example, if you have Java package with product key junit/junit, then you have to encode this value as: `java/junit/junit`.
+
+
+It supports also `--format` flag with same values.
+
+  ```
+    $> veye info java/junit/junit
+    Asking information about: junit/junit
+  ```
+  
+  ![Pretty print](https://s3-eu-west-1.amazonaws.com/veye/info_format_pretty2.png)
+  
+
+### Products 
+
+This command has subcommands to control your personal connections with libraries.
+
+```
+	;;follow some package to add it into your RSS feed
+	$> veye products follow clojure/ztellman/aleph
+	$> veye products unfollow clojure/ztellman/aleph
+	
+	;; show the list of products in your's RSS feed
+	$> veye products
+```
+
+### Check
+
+Use `check` command to upload your project file and check the state of dependencies. **NB!** it only shows information about dependencies, if you need also project info, then please use `veye project upload` command.
+
+```
+ $> veye check test/files/Gemfile
+```
+
+### Project
+
+The `project` command holds a multiple subcommands for working with our project files.
+
+###### show existing projects
+
+```
+  $> veye projects list
+  $> veye projects --format=table
+```
+
+###### show information of specific project
+
+A `show` command expects a proper project_key, which you can from the list of already existing projects.
+
+```
+	$> veye projects show rubygem_gemfile_1
+	$> veye projects show rubygem_gemfile_1 --format=table
+```
+
+###### upload project file
+
+Use `upload` command to create new project. This command expects proper filepath to the file and the file is smaller than 500KB. VersionEye supports currently 8 different package managers(*Leiningen, Gem, Maven, NPM, Packagist, Pip, Setup.py, R*), Bower and Obj-C is already on pipeline.
+
+```
+  $> veye projects upload test/files/Gemfile
+  $> veye projects upload test/files/maven.pom
+```
+
+###### re-upload project file for existing project
+
+You can use `update` command to update the information of already existing project.
+This command expects correct project_key and a path to file.
+
+```
+  $> veye projects update rubygem_gemfile_1 test/files/Gemfile
+  $> veye projects update rubygem_gemfile_1 test/files/Gemfile --format=table
+```
+
+###### Delete project
+
+This command removes the specified project from your project's list.
+
+```
+	$> veye projects delete rubygem_gemfile_1
+	Deleted
+```
+
+###### Licences
+
+`licence` command returns all licenses used in your project.
+
+```
+	$> veye projects licences rubygem_gemfile_1 --format=table
+```
+
+
+### Me
+
+`me` command returns short overview of your profile and your current payment plan.
+
+```
+	$> veye me
+``` 
+
+####### Favorite packages
+
+`me` command has a `favorite` command, which returns all packages you're currently following.
+
+```
+ $> veye me favorites
+ $> veye me favorites --page=2
+```

data/README.rdoc

@@ -0,0 +1,6 @@
+= veye
+
+Describe your project here
+
+:include:veye.rdoc
+

data/Rakefile

@@ -0,0 +1,44 @@
+require 'rake/clean'
+require 'rubygems'
+require 'rubygems/package_task'
+require 'rdoc/task'
+require 'cucumber'
+require 'cucumber/rake/task'
+Rake::RDocTask.new do |rd|
+  rd.main = "README.rdoc"
+  rd.rdoc_files.include("README.rdoc","lib/**/*.rb","bin/**/*")
+  rd.title = 'VersionEye Commandline Tool'
+end
+
+spec = eval(File.read('veye.gemspec'))
+
+Gem::PackageTask.new(spec) do |pkg|
+end
+CUKE_RESULTS = 'results.html'
+CLEAN << CUKE_RESULTS
+desc 'Run features'
+Cucumber::Rake::Task.new(:features) do |t|
+  opts = "features --format html -o #{CUKE_RESULTS} --format progress -x"
+  opts += " --tags #{ENV['TAGS']}" if ENV['TAGS']
+  t.cucumber_opts =  opts
+  t.fork = false
+end
+
+desc 'Run features tagged as work-in-progress (@wip)'
+Cucumber::Rake::Task.new('features:wip') do |t|
+  tag_opts = ' --tags ~@pending'
+  tag_opts = ' --tags @wip'
+  t.cucumber_opts = "features --format html -o #{CUKE_RESULTS} --format pretty -x -s#{tag_opts}"
+  t.fork = false
+end
+
+task :cucumber => :features
+task 'cucumber:wip' => 'features:wip'
+task :wip => 'features:wip'
+require 'rake/testtask'
+Rake::TestTask.new do |t|
+  t.libs << "test"
+  t.test_files = FileList['test/*_test.rb']
+end
+
+task :default => [:test,:features]