readme.md in invoker-0.0.3 vs readme.md in invoker-0.1.1.pre

- old
+ new

@@ -20,11 +20,10 @@ [dj] directory = /home/gnufied/god_particle command = zsh -c 'bundle exec ruby script/delayed_job' - [events] directory = /home/gnufied/god_particle command = zsh -c 'bundle exec ruby script/event_server' After that you can start process manager via: @@ -42,12 +41,21 @@ ~> invoker remove dj -s 9 # add and start running ~> invoker add dj -You can also enable OSX notifications for crashed processes by installing `terminal-notification` gem. It is not a dependency, but can be useful if something crashed and you weren't paying attention. + # List currently running processes managed by invoker + ~> invoker list + # Restart process given by command Label + ~> invoker reload dj + + # Restart process given by command label using specific signal for killing + ~> invoker reload dj -s 9 + +You can also enable OSX notifications for crashed processes by installing `terminal-notifier` gem. It is not a dependency, but can be useful if something crashed and you weren't paying attention. + ## Using with rbenv or rvm ## The way `rbenv` and `rvm` work sometimes creates problems when you are trying to use a process supervisor like `invoker`. There are couple of things to keep in mind, If you are running `invoker` with Ruby version x, but your application requires Ruby version Y: @@ -56,10 +64,10 @@ command = RBENV_VERSION=2.0.0-p0 zsh -c "bundle exec rails s" * Unless version of Ruby using which you are running `invoker` command and version of Ruby you are using in the application is same, you almost always will want to use `zsh -c` or `bash -c`. `RVM` in particular requires a login shell and hence sometimes you may have to use `bash -lc`. For example: - command = bash -lc "rvm use 2.0.0-p0 && bundle exec rails s" + command = bash -lc "rvm 2.0.0-p0 do bundle exec rails s" ## Bug reports and Feature requests Please use [Github Issue Tracker](https://github.com/code-mancers/invoker/issues) for feature requests or bug reports.