Guard-rails is watching on your railses!
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 growing!
:daemon
runs the server as a daemon, without any output to the terminal that ranguard
(defaultfalse
):debugger
enable the debugger in server. Required ruby-debug gem. (defaultfalse
):environment
is the server environment (defaultdevelopment
):force_run
kills any process that's holding the listen port before attempting to (re)start Rails (defaultfalse
):pid_file
specify your pid_file (defaulttmp/pids/[RAILS_ENV].pid
):port
is the server port number (default3000
):server
the webserver engine to use (try:server => :thin
):start_on_start
will start the server when starting Guard (defaulttrue
):timeout
waits when restarting the Rails server, in seconds (default30
).:zeus_plan
the custom plan in zeus, only works whenzeus
option istrue
(defaultserver
):zeus
support zeus to boost rails init speed (defaultfalse
).:CLI
construct the runner command as your willing! Will omit all options above exceptpid_file
! (defaultrails server --pid tmp/pids/[RAILS_ENV].pid
)
How-to
- Multiple instances use
pid_file
option to run multiple instances with same rails_env
Contribute
Feel free to fork'n'fix for any willing.
Or
Tell.me in: any.way