No longer maintained. Latest version is at https://github.com/ranmocy/guard-rails
36d24c0c14 | ||
---|---|---|
lib | ||
spec | ||
.gitignore | ||
.travis.yml | ||
Gemfile | ||
Guardfile | ||
README.md | ||
Rakefile | ||
guard-rails.gemspec |
README.md
This fork is no longer maintained. Visit https://github.com/ranmocy/guard-rails for the current official fork.
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 (default3000
):environment
is the environment to use (defaultdevelopment
):start_on_start
will start the server when starting Guard (defaulttrue
):force_run
kills any process that's holding open the listen port before attempting to (re)start Rails (defaultfalse
).:daemon
runs the server as a daemon, without any output to the terminal that ranguard
(defaultfalse
).:debugger
runs the server with the debugger enabled (defaultfalse
). Required ruby-debug gem.:timeout
waits this number of seconds when restarting the Rails server before reporting there's a problem (default20
).:server
lets you specify the webserver engine to use (try:server => :thin
).
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.