lockpick 1.0.1 → 1.0.2

data/README.md

@@ -1,24 +1,44 @@
 # Lockpick
 
-TODO: Write a gem description
+Allowing SSH access to the members of a GitHub team.
 
 ## Installation
 
-Add this line to your application's Gemfile:
+```lockpick``` is meant to be run as a script. You can either install it via Rubygems:
 
-    gem 'lockpick'
-
-And then execute:
+    $ gem install lockpick
 
-    $ bundle
+You may need to use ```sudo``` if you are installing against the system Ruby...
+    
+Or clone this repo:
 
-Or install it yourself as:
+    $ git clone https://github.com/fredjean/lockpick.git
 
-    $ gem install lockpick
+You will probably need to run ```bundle install``` if you choose that path...
 
 ## Usage
 
-TODO: Write usage instructions here
+```lockpick``` is a simple script that uses the GitHub APIs to retrieve the list of verified, public ssh keys for the
+members of one or more teams.
+
+All you need to do to run the lockpick script:
+
+    $ lockpick
+
+You can also use cron to run it periodically. Adding the following line to your crontab:
+
+    5 * * * * 
+
+## First Run
+
+The script uses [Ara's Main](https://github.com/ahoward/main) gem to run. It will open up an editor with a template
+configuration:
+
+```ruby
+```
+
+It will then proceed to pull the keys from GitHub. The configuration is stored under ```~/.lockpick/config.yml```
+
 
 ## Contributing
 

data/bin/lockpick

@@ -26,6 +26,9 @@ Main {
   })
 
   def run
+    status = lock_file.flock(File::LOCK_EX|File::LOCK_NB)
+    exit(42) unless status == 0
+
     pull_ssh_keys!
   end
 
@@ -65,6 +68,10 @@ Main {
     github.users.keys.list(user: login).response.body
   end
 
+  def lock_file
+    @lock_file ||= File.open(File.join(state_path, ".lock"), 'w')
+  end
+
   mode(:shell) {
     def run
       require 'pry'
@@ -78,9 +85,6 @@ Main {
 
 
 BEGIN {
-  status = DATA.flock(File::LOCK_EX|File::LOCK_NB)
-  exit(42) unless status == 0
-
   require 'rubygems'
   require 'github_api'
   require 'map'
@@ -153,5 +157,9 @@ BEGIN {
   end
 }
 
+END {
+  lock_file.close
+}
+
 __END__
 ### We need something to lock on...

data/lib/lockpick/version.rb

@@ -1,3 +1,3 @@
 module Lockpick
-  VERSION = "1.0.1"
+  VERSION = "1.0.2"
 end

data/lockpick.gemspec

@@ -13,7 +13,9 @@ Gem::Specification.new do |spec|
   spec.homepage      = "https://github.com/fredjean/lockpick"
   spec.license       = "MIT"
 
-  spec.files         = `git ls-files`.split($/)
+  spec.files         = `git ls-files`.split($/).reject do |f|
+    %w(Cheffile Cheffile.lock Vagrantfile upgrade-chef.sh).include?(f)
+  end
   spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
   spec.require_paths = ["lib"]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: lockpick
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-06-24 00:00:00.000000000 Z
+date: 2013-06-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: main
@@ -148,18 +148,14 @@ extensions: []
 extra_rdoc_files: []
 files:
 - .gitignore
-- Cheffile
-- Cheffile.lock
 - Gemfile
 - LICENSE.txt
 - README.md
 - Rakefile
-- Vagrantfile
 - bin/lockpick
 - lib/lockpick.rb
 - lib/lockpick/version.rb
 - lockpick.gemspec
-- upgrade-chef.sh
 homepage: https://github.com/fredjean/lockpick
 licenses:
 - MIT
@@ -175,7 +171,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 4571190319562877000
+      hash: -1573546165165272002
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -184,7 +180,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 4571190319562877000
+      hash: -1573546165165272002
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23

data/Cheffile

@@ -1,7 +0,0 @@
-site 'http://community.opscode.com/api/v1'
-
-cookbook 'apt'
-cookbook 'rbenv', :git => 'git://github.com/fnichol/chef-rbenv.git'
-cookbook 'ruby_build'
-cookbook 'vim'
-cookbook 'build-essential'

data/Cheffile.lock

@@ -1,20 +0,0 @@
-SITE
-  remote: http://community.opscode.com/api/v1
-  specs:
-    apt (2.0.0)
-    build-essential (1.4.0)
-    ruby_build (0.8.0)
-
-GIT
-  remote: git://github.com/fnichol/chef-rbenv.git
-  ref: master
-  sha: 9afb4e5da2e6212504a12de3bbbd410cd96100f6
-  specs:
-    rbenv (0.7.3)
-
-DEPENDENCIES
-  apt (>= 0)
-  build-essential (>= 0)
-  rbenv (>= 0)
-  ruby_build (>= 0)
-

data/Vagrantfile

@@ -1,126 +0,0 @@
-# -*- mode: ruby -*-
-# vi: set ft=ruby :
-
-Vagrant.configure("2") do |config|
-  # All Vagrant configuration is done here. The most common configuration
-  # options are documented and commented below. For a complete reference,
-  # please see the online documentation at vagrantup.com.
-
-  # Every Vagrant virtual environment requires a box to build off of.
-  config.vm.box = "ubuntu-precise-64"
-
-  # The url from where the 'config.vm.box' box will be fetched if it
-  # doesn't already exist on the user's system.
-  config.vm.box_url = "http://files.vagrantup.com/precise64.box"
-
-  # Create a forwarded port mapping which allows access to a specific port
-  # within the machine from a port on the host machine. In the example below,
-  # accessing "localhost:8080" will access port 80 on the guest machine.
-  # config.vm.network :forwarded_port, guest: 80, host: 8080
-
-  # Create a private network, which allows host-only access to the machine
-  # using a specific IP.
-  # config.vm.network :private_network, ip: "192.168.33.10"
-
-  # Create a public network, which generally matched to bridged network.
-  # Bridged networks make the machine appear as another physical device on
-  # your network.
-  # config.vm.network :public_network
-
-  # Share an additional folder to the guest VM. The first argument is
-  # the path on the host to the actual folder. The second argument is
-  # the path on the guest to mount the folder. And the optional third
-  # argument is a set of non-required options.
-  # config.vm.synced_folder "../data", "/vagrant_data"
-
-  # Provider-specific configuration so you can fine-tune various
-  # backing providers for Vagrant. These expose provider-specific options.
-  # Example for VirtualBox:
-  #
-  # config.vm.provider :virtualbox do |vb|
-  #   # Don't boot with headless mode
-  #   vb.gui = true
-  #
-  #   # Use VBoxManage to customize the VM. For example to change memory:
-  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
-  # end
-  #
-  # View the documentation for the provider you're using for more
-  # information on available options.
-
-  # Enable provisioning with Puppet stand alone.  Puppet manifests
-  # are contained in a directory path relative to this Vagrantfile.
-  # You will need to create the manifests directory and a manifest in
-  # the file base.pp in the manifests_path directory.
-  #
-  # An example Puppet manifest to provision the message of the day:
-  #
-  # # group { "puppet":
-  # #   ensure => "present",
-  # # }
-  # #
-  # # File { owner => 0, group => 0, mode => 0644 }
-  # #
-  # # file { '/etc/motd':
-  # #   content => "Welcome to your Vagrant-built virtual machine!
-  # #               Managed by Puppet.\n"
-  # # }
-  #
-  # config.vm.provision :puppet do |puppet|
-  #   puppet.manifests_path = "manifests"
-  #   puppet.manifest_file  = "init.pp"
-  # end
-
-  # Enable provisioning with chef solo, specifying a cookbooks path, roles
-  # path, and data_bags path (all relative to this Vagrantfile), and adding
-  # some recipes and/or roles.
-  #
-
-  config.vm.provision :shell, path: 'upgrade-chef.sh'
-  config.vm.provision :chef_solo do |chef|
-    chef.cookbooks_path = "cookbooks"
-    chef.add_recipe('apt')
-    chef.add_recipe('build-essential')
-    chef.add_recipe('ruby_build')
-    chef.add_recipe('rbenv::system')
-    chef.add_recipe('vim')
-    chef.add_recipe('rbenv::vagrant')
-
-    # You may also specify custom JSON attributes:
-    chef.json = {
-      rbenv: {
-        rubies: [ "1.9.3-p385" ],
-        upgrade: 'sync',
-        global: '1.9.3-p385',
-        gems: {
-          '1.9.3-p385' => [
-            { name: 'bundler' }
-          ]
-        }
-      }
-    }
-  end
-
-  # Enable provisioning with chef server, specifying the chef server URL,
-  # and the path to the validation key (relative to this Vagrantfile).
-  #
-  # The Opscode Platform uses HTTPS. Substitute your organization for
-  # ORGNAME in the URL and validation key.
-  #
-  # If you have your own Chef Server, use the appropriate URL, which may be
-  # HTTP instead of HTTPS depending on your configuration. Also change the
-  # validation key to validation.pem.
-  #
-  # config.vm.provision :chef_client do |chef|
-  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
-  #   chef.validation_key_path = "ORGNAME-validator.pem"
-  # end
-  #
-  # If you're using the Opscode platform, your validator client is
-  # ORGNAME-validator, replacing ORGNAME with your organization name.
-  #
-  # If you have your own Chef Server, the default validation client name is
-  # chef-validator, unless you changed the configuration.
-  #
-  #   chef.validation_client_name = "ORGNAME-validator"
-end

data/upgrade-chef.sh

@@ -1,6 +0,0 @@
-#!/usr/bin/env bash
-
-sudo apt-get update
-sudo apt-get -y install curl
-
-sudo true && curl -L https://www.opscode.com/chef/install.sh | sudo bash