No longer maintained. Latest version is at https://github.com/ranmocy/guard-rails
Go to file
Sidney Burks d795068894 kill -INT not kiling process on linux. switched to kill -KILL 2011-06-20 03:14:53 +02:00
lib kill -INT not kiling process on linux. switched to kill -KILL 2011-06-20 03:14:53 +02:00
spec write some tests 2011-06-03 09:18:16 -04:00
.gitignore initial commit 2011-05-27 14:41:07 -04:00
.travis.yml fix travis.yml 2011-06-06 15:02:32 -04:00
Gemfile clean up testing some more 2011-06-06 09:49:58 -04:00
Guardfile add deamonize option and start some tests 2011-06-01 10:06:35 -04:00
README.md readme 2011-06-05 07:27:02 -04:00
Rakefile update rakefile 2011-06-18 12:40:53 -04:00
guard-rails.gemspec add deamonize option and start some tests 2011-06-01 10:06:35 -04:00

README.md

Build Status

Want to restart your Rails development server whilst you work? Now you can!

guard 'rails', :port => 5000 do
  watch('Gemfile.lock')
  watch(%r{^(config|lib)/.*})
end

Lots of fun options!

  • :port is the port number to run on (default 3000)
  • :environment is the environment to use (default development)
  • :start_on_start will start the server when starting Guard (default true)
  • :force_run kills any process that's holding open the listen port before attempting to (re)start Rails (default false).
  • :daemon runs the server as a daemon, without any output to the terminal that ran guard (default false).
  • :timeout waits this number of seconds when restarting the Rails server before reporting there's a problem (default 20).

This is super-alpha, but it works for me! Only really hand-tested in Mac OS X. Feel free to fork'n'fix for other OSes, and to add some more real tests.