hrk 0.0.4 → 0.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 172ab5ee4bd7bf4c32959c037180e9d0cba6b1ff
-  data.tar.gz: 7d03ead725cf5599a4262cc6b7a9cc095ee0bff8
+  metadata.gz: c55c5d03bcb00380ffcff94955234658934ee118
+  data.tar.gz: 72e2a53ee349c5dbaece355c70b89085dc72827f
 SHA512:
-  metadata.gz: 307c5ffa6b227953e064367f35ec37b25ebc46e0e18b4abb99b358b1839bbb975d9218292691a3dde17bce86ebbf3272022fa5ad456696cfc9abbfe17e91ecdf
-  data.tar.gz: fd7c224100e26d2cc70b64f7eb69f10b923d13a8601207cfddc2f0dcced6379866f4c60cf6ce3b96bbed7be0cebcddb6af7bc7037bb112b126986555a75d4c1b
+  metadata.gz: 4c5dfad9f5057ce40bda69d34dca06ccac6d068be94e607efabb66d29e08e7f838e72e5e58128e66d732b7e2ea31d52fda5f12e3dbb6f89cec7bb7e0626c4c1f
+  data.tar.gz: 57f0447db88c4739215ed04c94f046e12db6da9983d2c048d34c3c0576c9c10076af74960824e4eb6d156d48688e87f46dd0a3f840f7aa62adcf0393859e1825

data/README.md

@@ -21,66 +21,100 @@ $ bundle install
 
 And enjoy the hrk command awesome power:
 ```
-$ hrk your-heroku-remote-name logs
+$ hrk your-heroku-remote-name: logs && hrk : run console
 ```
 
 
 ## What does it do?
 
-It's a command that calls the heroku toolbelt command for you, using your local
-heroku git remote name instead of that app's name.
+It's a command that calls the heroku toolbelt command for you, remembers the
+name of the previous remote so you don't have to re-type it again and again
+and again each time you want to chain heroku commands.
 
 For example, let's say I've got an heroku app that's called:
 
-> this-really-long-app-name
+> this-really-long-remote-name
 
 Well, I type my heroku commands like:
 
-```
-$ heroku run rake do:stuff
+```bash
+$ heroku run rake do:stuff -r this-really-long-remote-name
 ```
 
 And it's easy.
 
-Yep, but now I need a staging environment and a testing environment, so I add
-other heroku repositories that I aptly call:
+Yep, but now I want to chain my commands:
 
-```
-this-really-long-app-name-that-is-used-as-a-demo
-this-really-long-app-name-draft
+```bash
+$ heroku run rake do:something:else -r this-really-long-remote-name && \
+  heroku run rake other:thing       -r this-really-long-remote-name && \
+  heroku run rake yet:another:task  -r this-really-long-remote-name
 ```
 
-Now all my heroku commands look like:
+And sometimes you mistype, and the chain breaks in the middle, and it sucks.
 
-```
-$ heroku run rake do:something:else -a this-really-long-app-name
-$ heroku run rake other:thing -a this-really-long-app-name-that-is-used-as-a-demo
-$ heroku run rake yet:another:task -a this-really-long-app-name-draft
+**Wait, I can do something like that**
+
+```bash
+$ export REMOTE_NAME=this-really-long-remote-name && \
+  heroku run rake do:something:else -r $REMOTE_NAME && \
+  heroku run rake other:thing       -r $REMOTE_NAME && \
+  heroku run rake yet:another:task  -r $REMOTE_NAME
 ```
 
-And, let's be frank, that sucks even when I don't have to chain these commands.
+Yup. Now It doesn't look really that better now does it?
 
 **Hrk to the rescue!**
 
-Now, if you're like me, you've probably named your various heroku remotes in a
-more sensible way than just your heroku app names, for example:
+Hrk remembers the previous remote you've used. So you can do:
 
+```bash
+$ hrk this-relly-long-remote-name: run rake do:some:work && \
+  hrk : run rake arrange:stuff && \
+  hrk : run rake test:some:thingy
 ```
-prod    => this-really-long-app-name
-staging => this-really-long-app-name-that-is-used-as-a-demo
-test    => this-really-long-app-name-draft
-```
 
-Which means that you could call the Hrk command instead of the heroku command
-using your remotes names like:
+Isn't it more fun?
+
+## Wait, what happens when...
+
+**...I chain hrk commands with other bash commands?**
 
+No worry there, the previous remote will be remembered as long as you don't
+close your terminal.
+
+```bash
+$ git push demo && \
+  hrk demo: run rake set-this-once && \ # happens on demo
+  git push -f demo HEAD^ && \
+  hrk : restart                         # also on demo
 ```
-$ hrk prod    run rake do:some:work
-$ hrk staging run rake arrange:stuff
-$ hrk test    run rake test:some:thingy
+
+**...I chain hrk commands on concurrent terminals for different remotes?**
+
+No worry either, both terminals have their own memory and shouldn't overlap.
+Then:
+
+```bash
+# on terminal 1
+$ hrk demo: run rake db:migrate && \ # happens on demo
+  hrk : restart                      # still on demo
+# on terminal 2
+$ hrk prod: run rake db:migrate && \ # happens on prod
+  hrk : restart                      # still on prod
 ```
 
-Easy!
+**...I set another remote after completing a bunch of commands?**
+
+The last remote set is the one used by default for subsequent commands. So:
+
+```bash
+$ hrk demo: run rake db:migrate && \ # happens on demo
+  hrk : restart && \                 # also on demo
+  hrk prod: maintenance:on && \      # happens on prod
+  hrk : run rake db:migrate && \     # also on prod
+  hrk : maintenance:off              # still on prod
+```
 
 ## Do I still need the heroku toolbelt?
 

data/lib/hrk/execute/help.rb

@@ -16,8 +16,14 @@ module Hrk
       def display
         puts <<-eos
 Usage:
-  hrk remote: command..."
-  hrk [h | help | -h | --help]"
+  hrk [remote]: command...
+  hrk [h | help | -h | --help]
+
+hrk remembers the last remote you've used to send a command on this terminal,
+and use it by default when you omit the optional [remote] argument.
+
+The command is whatever you would give heroku, except (obviously) for the
+-r or -a argument.
 
 Options:
   -h --help Display this screen.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hrk
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.0.5
 platform: ruby
 authors:
 - Michel Belleville