gemnasium 3.2.1

data/.gitignore

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

data/.rvmrc

@@ -0,0 +1 @@
+rvm ruby-2.0.0-p0@gemnasium-gem --create

data/.travis.yml

@@ -0,0 +1,5 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0.0
+  - 2.1.2

data/CHANGELOG.md

@@ -0,0 +1,52 @@
+# 3.2.1 / 2014-11-27
+
+* Add deprecation warning
+
+# 3.2.0 / 2014-06-26
+
+* [#15][] Add --silence-branch option to the 'push' command
+
+* [#15][] Add --silence-branch option to the 'push' command
+
+# 3.1.0 / 2014-06-03
+
+* [#10][] Add --ignore-branch option to the 'push' command
+* Parse ERB code in the configuration file
+
+# 3.0.1 / 2014-02-11
+
+* Add support for Python and PHP Composer dependency files
+
+# 3.0.0 / 2014-02-10
+
+**API V2 is now deprecated and all previous gem releases have been yanked**
+
+* Update config file syntax: replace `profile_name` with `project_slug`
+* Add `migrate` command to migrate the config file from previous versions
+* Add `resolve` command to find a project that matches a name and a branch
+* Make it compatible with Gemnasium API v3
+
+# 2.0.2 / 2013-07-31
+
+* [#6][] Fix spec for fedora packaging (@ktdreyer)
+
+# 2.0.1 / 2013-07-25
+
+* Update regexp to fetch dependency files in subrepositories.
+
+# 2.0.0 / 2013-04-30
+
+**API V1 is now deprecated and all previous gem releases have been yanked**
+
+* Drop `project_visibility` option, all offline projects are private now
+* Add `ignored_paths` options to avoid pushing useless files
+
+# 1.0.1 / 2013-04-02
+
+* Fix Git after-commit hook (drop Perl style regexp) (revealed by @veilleperso)
+* Fix Gem's description
+
+# 1.0.0 / 2013-03-05
+
+Initial release
+

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in gemnasium.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Tech-Angels LLC
+
+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,157 @@
+# Gemnasium gem
+[![Dependency Status](https://gemnasium.com/gemnasium/gemnasium-gem.png)](https://gemnasium.com/gemnasium/gemnasium-gem)
+[![Build Status](https://travis-ci.org/gemnasium/gemnasium-gem.png?branch=master)](https://travis-ci.org/gemnasium/gemnasium-gem)
+
+**Gemnasium gem has been deprecated. Please use the [Gemnasium Toolbelt](https://github.com/gemnasium/toolbelt) instead!**
+
+This gem lets you push your dependency files to [Gemnasium](https://gemnasium.com/) to track your project's dependencies and get notified about updates and security advisories.
+
+Gemnasium app offers Github integration with fully automated synchronization but you can use this gem if you don't want to authorize access to your repositories (ie: for privacy concern).
+
+Supported dependency files are:
+
+* Ruby: `Gemfile`, `Gemfile.lock` and `*.gemspec`
+* NPM: `package.json` and `npm-shrinkwrap.json`
+* Python: `requirements.txt`, `setup.py` and `requires.txt`
+* PHP Composer: `composer.json` and `composer.lock`
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'gemnasium'
+
+Or in your terminal:
+
+    $ gem install gemnasium
+
+Add configuration file in your project
+
+    $ gemnasium install
+
+Install command supports 2 options : `--rake` and `--git` to respectively install the gemnasium [rake task](#2-via-the-rake-task) and a [post-commit git hook](#3-via-the-post-commit-git-hook).
+
+`gemnasium install` will add the config/gemnasium.yml file to your .gitignore so your private API key won't be committed. If you use another versionning system, please remember to ignore this file.
+
+__Warning: your api key is dedicated to your own user account and must not be published!__
+
+Fill the values of the new config/gemnasium.yml file.
+
+## Migrate from previous versions
+
+Migrate your configuration file:
+
+    $ gemnasium migrate
+
+Convert your project name to a unique "project slug":
+
+    $ gemnasium resolve
+
+The `resolve` command will update your configuration file.
+
+## Usage
+
+There is multiple ways to use the gemnasium gem. You can choose whichever you prefer.
+
+### 1. Via the command line
+
+Using gemnasium from the command line is as simple as typing `gemnasium [command]` :
+
+__To create a project on Gemnasium:__
+
+    $ gemnasium create
+
+Create command will look for data in your config/gemnasium.yml configuration file to create a project.
+
+Please note that automatic Github synchronization will be dropped once project is configured with this gem.
+
+__To push your dependency files on Gemnasium:__
+
+    $ gemnasium push
+
+### 2. Via the rake task
+
+Gemnasium gem comes with a rake task ready to be used. To use it, you need to install it via: `gemnasium install --rake`
+Once installed, you'll have access to 2 tasks:
+
+__To create a project on Gemnasium:__
+
+    $ rake gemnasium:create
+
+Create command will look for data in your config/gemnasium.yml configuration file to create a project.
+
+Please note that automatic Github synchronization will be dropped once project is configured with this gem.
+
+__To push your dependency files on Gemnasium:__
+
+    $ rake gemnasium:push
+
+### 3. Via the post-commit git hook
+
+We wrote for you a ready-to-use [post-commit git hook](lib/templates/post-commit).
+
+Once installed via `gemnasium install --git`, the gem will push your dependency files after each commit only if they have changed.
+
+### 4. Directly in your code
+
+If you need to use Gemnasium gem right into your code, you can do so just like below:
+
+```ruby
+require 'gemnasium'
+
+
+# To install gemnasium files
+#
+# options is a Hash which can contain the following keys:
+#   project_path (required) - [String] path to the project
+#   install_rake_task       - [Boolean] whether or not to install the rake task
+#   install_git_hook        - [Boolean] whether or not to install the git hook
+Gemnasium.install(options)
+
+# To create your project on gemnasium
+#
+# options is a Hash which can contain the following keys:
+#   project_path (required) - [String] path to the project
+Gemnasium.create_project(options)
+
+# To push supported dependency files to gemnasium
+#
+# options is a Hash which can contain the following keys:
+#   project_path (required) - [String] path to the project
+Gemnasium.push(options)
+```
+
+## Sample config
+
+Here is a sample config file:
+
+```yaml
+api_key: "some_secret_api_key"
+project_name: "vandamme"
+project_slug: "40d7fafbc32fe0c9e5b84ecacd71012c"
+project_branch: "master"
+ignored_paths:
+  - spec/
+  - tmp/
+```
+
+This will handle the dependencies of the _vandamme_ project on _master_ branch.
+Gemnasium gem will also ignore the project dependency files found in _spec/_ and _tmp/_.
+
+## Troubleshooting
+
+Gemnasium will try to display the most accurate error message when something goes wrong.
+
+Though, if you're stil stuck with something, feel free to contact [Gemnasium support](http://support.gemnasium.com).
+
+## Contributing
+
+1. Fork the project.
+2. Make your feature or bug fix.
+3. Test it.
+4. Commit.
+5. Create new pull request.
+
+## Credits
+
+[![Tech-Angels](http://media.tumblr.com/tumblr_m5ay3bQiER1qa44ov.png)](http://www.tech-angels.com)

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new('spec')
+
+task :default => :spec

data/bin/gemnasium

@@ -0,0 +1,43 @@
+#!/usr/bin/env ruby
+#Adjust path in case called directly and not through gem
+$:.unshift "#{File.expand_path(File.dirname(__FILE__))}/../lib"
+
+require 'gemnasium'
+require 'gemnasium/options'
+require 'gemnasium/version'
+
+#Parse options
+begin
+  options, parser = Gemnasium::Options.parse ARGV
+rescue OptionParser::ParseError => e
+  $stderr.puts e.message.capitalize
+  $stderr.puts "Please see `gemnasium --help` for valid options"
+  abort
+end
+
+if options[:show_help]
+  puts parser
+  exit
+elsif options[:show_version]
+  puts "gemnasium v#{Gemnasium::VERSION}"
+  exit
+end
+
+# Set project path
+options[:project_path] = File.expand_path(".")
+
+case options[:command]
+when 'create'
+  Gemnasium.create_project options
+when 'install'
+  Gemnasium.install options
+when 'push'
+  Gemnasium.push options
+when 'migrate'
+  Gemnasium.migrate options
+when 'resolve'
+  Gemnasium.resolve_project options
+else
+  $stdout.puts "Please see `gemnasium --help` for valid options"
+  exit
+end

data/features/gemnasium.feature

@@ -0,0 +1,58 @@
+Feature: Help messages about gemnasium gem
+
+  By using gemnasium [options], the user is able to get helpfull messages
+  about how to use the gemnasium gem.
+
+  Scenario: Without options
+    When I run `gemnasium`
+    Then the output should contain "Please see `gemnasium --help` for valid options"
+    And the exit status should be 0
+
+  Scenario: With invalid option
+    When I run `gemnasium -z`
+    Then the output should contain exactly:
+      """
+      Invalid option: -z
+      Please see `gemnasium --help` for valid options\n
+      """
+    And the exit status should be 1
+
+  Scenario Outline: With version option
+    When I run `gemnasium <option>`
+    Then the output should contain exactly:
+      """
+      gemnasium v3.2.1\n
+      """
+    And the exit status should be 0
+
+    Scenarios: Version options
+      | option    |
+      | -v        |
+      | --version |
+
+  Scenario Outline: With version option
+    When I run `gemnasium <option>`
+    Then the output should contain exactly:
+      """
+      Usage: gemnasium [options]
+          -v, --version                    Show Gemnasium version
+          -h, --help                       Display this message
+
+      Available commands are:
+        create   :   Create or update project on Gemnasium
+        install  :   Install the necessary config file
+        push     :   Push your dependency files to Gemnasium
+        migrate  :   Migrate the configuration file
+        resolve  :   Resolve project name to an existing project on Gemnasium
+
+      See `gemnasium COMMAND --help` for more information on a specific command.
+
+      WARNING! The gemnasium Rubygem has been deprecated.
+      Please use Gemnasium Toolbelt (https://github.com/gemnasium/toolbelt) instead.\n
+      """
+    And the exit status should be 0
+
+    Scenarios: Version options
+      | option  |
+      | -h      |
+      | --help  |

data/features/gemnasium_create.feature

@@ -0,0 +1,13 @@
+Feature: Create or update a project on Gemnasium
+
+  By using gemnasium create [options], the user is able to create a new
+  project on Gemnasium. The user cannot create a project if the configuration
+  already refers to an existing project.
+
+  Scenario: Without configuration file
+    Given a directory named "project/foo/bar"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium create`
+    Then the output should contain "/config/gemnasium.yml) does not exist."
+    And the output should contain "Please run `gemnasium install`."
+    And the exit status should be 1

data/features/gemnasium_install.feature

@@ -0,0 +1,119 @@
+Feature: Create or update a project on Gemnasium
+
+  By using gemnasium install [options], the user is able to install
+  the necessary files to run gemnasium.
+
+  Scenario: Without option for a clean repo
+    Given a directory named "project/foo/bar"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install`
+    Then it should create the config directory
+    And it should create the config file
+    And the exit status should be 0
+
+  Scenario: Without option for a repo with a config directory
+    Given a directory named "project/foo/bar/config"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install`
+    Then it should create the config file
+    And the exit status should be 0
+
+  Scenario: Without option for a repo with the config file already installed
+    Given an empty file named "project/foo/bar/config/gemnasium.yml"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install`
+    Then the output should match:
+      """
+      The file .+\/config\/gemnasium.yml already exists
+      """
+    And the exit status should be 0
+
+  Scenario: With git option for a non git repo
+    Given a directory named "project/foo/bar"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install --git`
+    Then it should create the config directory
+    And it should create the config file
+    And the output should match:
+      """
+      .*\/project\/foo\/bar is not a git repository\. Try to run `git init`\.
+      """
+    And the file ".git/hooks/post-commit" should not exist
+    And the exit status should be 0
+
+  Scenario: With git option for git repo without post-commit hook
+    Given a directory named "project/foo/bar"
+    And I cd to "project/foo/bar"
+    And I run `git init`
+    When I run `gemnasium install --git`
+    Then it should create the config directory
+    And it should create the config file
+    And it should create the post-commit hook
+    And the exit status should be 0
+
+  Scenario: With git option for git repo with a post-commit hook file
+    Given a directory named "project/foo/bar"
+    And I cd to "project/foo/bar"
+    And I run `git init`
+    And an empty file named ".git/hooks/post-commit"
+    When I run `gemnasium install --git`
+    Then it should create the config directory
+    And it should create the config file
+    And the output should match:
+      """
+      The file .+\/.git\/hooks\/post-commit already exists
+      """
+    And the exit status should be 0
+
+  Scenario: With rake option for a repo without Rakefile
+    Given a directory named "project/foo/bar"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install --rake`
+    Then it should create the config directory
+    And it should create the config file
+    And the output should contain "Rakefile not found."
+    And the file "lib/tasks/gemnasium.rake" should not exist
+    And the exit status should be 0
+
+  Scenario: With rake option for a repo with a Rakefile without lib/tasks directory
+    Given an empty file named "project/foo/bar/Rakefile"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install --rake`
+    Then it should create the config directory
+    And it should create the config file
+    And it should create the tasks directory
+    And it should create the task file
+    And the exit status should be 0
+
+  Scenario: With rake option for a repo with a Rakefile with a lib/tasks directory
+    Given an empty file named "project/foo/bar/Rakefile"
+    And a directory named "project/foo/bar/lib/tasks"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install --rake`
+    Then it should create the config directory
+    And it should create the config file
+    And it should create the task file
+    And the exit status should be 0
+
+  Scenario: With rake option for a repo with the rake tasks already installed
+    Given an empty file named "project/foo/bar/Rakefile"
+    And an empty file named "project/foo/bar/lib/tasks/gemnasium.rake"
+    And I cd to "project/foo/bar"
+    When I run `gemnasium install --rake`
+    Then it should create the config directory
+    And it should create the config file
+    And the output should match:
+      """
+      The file .+\/lib\/tasks\/gemnasium\.rake already exists
+      """
+    And the exit status should be 0
+
+  Scenario: With both rake and git options
+    Given an empty file named "project/foo/bar/Rakefile"
+    And I cd to "project/foo/bar"
+    And I run `git init`
+    When I run `gemnasium install --git --rake`
+    Then it should create the config directory
+    And it should create the config file
+    And it should create the task file
+    And it should create the post-commit hook