instapusher 0.0.7 → 0.0.8

data/README.md

@@ -4,18 +4,38 @@ Makes it easy to push to heroku.
 
 ## Installation
 
-Add this to Gemfile:
-
-    gem 'instapusher'
+    gem install instapusher
 
 ## Usage
 
-    rake instapusher
+    instapusher
+
+It detects a project name and a branch from the git repo. Else you can specify it from the command line like:
+
+    instapusher rails master
+
+
+After installing the gem you should register in the `http://instapusher.com`.
+Setup a project using the user and project name from the github. And create a config file `.instapusher` with api key.
+Example:
+
+    api_key: 123123123
+
+## Setup Instapusher server
+
+You can provide the env variable `LOCAL` like:
+
+    LOCAL=1 instapusher
+
+And instapusher will send requests to `http://localhost:3000` server.
+Another solution is use env variable `INSTAPUSHER_HOST`.
+
+    INSTAPUSHER_HOST=instapusher.com instapusher
 
-After installing the gem copy [this file](https://raw.github.com/gist/3098161/578dad8cd3933834712a8afdf33520221dbdb986/instapusher.yml) to `config/instapusher.yml` .
+Also there are other env variables like `INSTAPUSHER_PROJECT` and `INSTAPUSHER_BRANCH`.
+
+    INSTAPUSHER_HOST=instapusher.com INSTAPUSHER_PROJECT=rails INSTAPUSHER_BRANCH=master instapusher
 
-Change the contents of `config/instapusher.yml` as per your needs after
-reading rest of README.
 
 ## What problem it solves
 
@@ -26,60 +46,31 @@ members to review. However in order to review the work all the team
 members need to pull down the branch and fire up `rails server` and then
 review.
 
-We like to see things working. So we developed `push2heroku` to push a
+We like to see things working. So we developed `instapusher` to push a
 feature branch to heroku instantly with one command. Executing
-`push2heroku` prints a url and we put that url in the pull request so
+`instapusher` prints a url and we put that url in the pull request so
 that team members can actually test the feature.
 
 ## Here is how it works
 
-`push2heroku` reads the `push2heroku.yml` and executes those commands.
-It's that simple.
-
-Lets say that I am working in a branch called
-`76-facebook-authentication`. When I execute `push2heroku` then the
+Lets say that I am working with github project `nimbleshop` in a branch called
+`76-facebook-authentication`. When I execute `instapusher` then the
 application name under which it will be deployed to heroku will be
-`nimbleshop-76-facebook-neeraj`.
+`nimbleshop-76-facebook-ip`.
 
 `nimbleshop` is the name of the project.
 `76-facebook` is the first 10 letters of the branch name.
-`neeraj` is the first 5 letters of my github user name.
+`ip` is characters to mark the instance as temporal.
 
 So in this case the url of the application will be
-`http://nimbleshop-76-facebook-neeraj.herokuapp.com` .
+`http://nnimbleshop-76-facebook-ip.herokuapp.com` .
 
-In the `push2heroku.yml` file the keys `production` and `staging`
-are branch names. And these branches are special branches. For these
-branches the url generated will be just the application name and the
-branch name. For example if I execute `rake push2heroku` from `staging`
+There are two special branches `production` and `staging`.
+For these branches the url generated will be just the application name and the
+branch name. For example if I execute `instapusher` from `staging`
 branch then the heroku url will be
 `http://nimbleshop-staging.herokuapp.com`.
 
-However if I delete `staging` key from `push2heroku.yml` then `staging`
-is no longer a special branch and the heroku url would be
-`http://nimbleshop-staging-neeraj.herokuapp.com` .
-
-## Callbacks
-
-The new design of `push2heroku` is very flexible. Let's say that Artem
-wants to test something then he can add to `push2heroku.yml` something
-like this
-
-```
-regenerate_images:
-  - bundle exec heroku run rake db:regenerate_images --app <%=ENV['HEROKU_APP_NAME']%> --trace
-  - bundle exec heroku run rake db:post_image_cleanup --app <%=ENV['HEROKU_APP_NAME']%> --trace
-```
-
-Now to execute all the commands under key `regenrate_images` all he has to do is
-
-```
-rake push2heroku CALLBACKS=reset_db_using_fixtures,regenerate_images
-```
-
-Just comma separate all the tasks. It's that simple. Now `push2heroku` gives all the control to the developer.
-
 ## License
 
 `instapusher` is released under MIT License.
-

data/bin/instapusher

@@ -2,4 +2,4 @@
 
 require 'instapusher/commands'
 
-Instapusher::Commands.deploy
+Instapusher::Commands.deploy *ARGV[0..1]

data/lib/instapusher/commands.rb

@@ -8,14 +8,13 @@ module Instapusher
     DEFAULT_HOSTNAME = 'instapusher.com'
 
     def self.deploy(project_name=nil, branch_name=nil)
-
       hostname = ENV['INSTAPUSHER_HOST'] || DEFAULT_HOSTNAME
       hostname = "localhost:3000" if ENV['LOCAL']
 
       url          = "http://#{hostname}/heroku.json"
       git          = Git.new
-      branch_name  ||= git.current_branch
-      project_name ||= git.project_name
+      branch_name  ||= ENV['INSTAPUSHER_BRANCH'] || git.current_branch
+      project_name ||= ENV['INSTAPUSHER_PROJECT'] || git.project_name
 
       api_key = Instapusher::Configuration.api_key || ""
       if api_key.to_s.length == 0

data/lib/instapusher/git.rb

@@ -14,7 +14,9 @@ module Instapusher
     end
 
     def project_name
-      `git config remote.origin.url`.chop!.scan(/\/([^\/]+).git$/).flatten.first
+      result = `git config remote.origin.url`.chop!.scan(/\/([^\/]+)?$/).flatten.first
+      result.sub!(/\.git$/, '') if result
+      result
     end
   end
 end

data/lib/instapusher/version.rb

@@ -1,3 +1,3 @@
 module Instapusher
-  VERSION = "0.0.7"
+  VERSION = "0.0.8"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: instapusher
 version: !ruby/object:Gem::Version
-  version: 0.0.7
+  version: 0.0.8
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-03-08 00:00:00.000000000 Z
+date: 2013-04-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hashr
@@ -97,7 +97,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 3024614146394705757
+      hash: -2459523936242913019
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -106,7 +106,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 3024614146394705757
+      hash: -2459523936242913019
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23