Guard-rails is watching on your railses!
Currently, the official fork repository is at ranmocy/guard-rails. Please, come here and communicate with me.
Please make sure to have Guard installed before continuing.
Add Guard::Rails to your Gemfile:
group :development do
gem 'guard-rails'
endAdd the default Guard::Rails template to your Guardfile by running:
$ guard init railsNow I can automatically restart your Rails development server as your files change!
:daemon runs the server as a daemon, without any output to the terminal that started guard (default false):debugger enable the debugger in server. Requires ruby-debug gem. (default false):environment is the server environment (default development):force_run kills any process that's holding the listen port before attempting to (re)start Rails (default false):pid_file specify your pid_file (default tmp/pids/[RAILS_ENV].pid):host is where the server is hosted (default localhost):port is the server port number (default 3000):root lets you specify the Rails root, i.e. for using guard-rails to run a dummy app within an engine (try :root => '/spec/dummy').:server the webserver engine to use (try :server => :thin):start_on_start will start the server when starting Guard (default true):timeout waits when restarting the Rails server, in seconds (default 30).:zeus_plan the custom plan in zeus, only works when zeus option is true (default server):zeus support zeus to boost rails init speed (default false).:CLI construct the runner command as you will! Will omit all options above except pid_file! (default rails server --pid tmp/pids/[RAILS_ENV].pid)pid_file option to run multiple instances with same rails_env.The best way to contact me is the Issues and Pull Request system on GitHub. Currently the official fork repository is at ranmocy/guard-rails.
Please, post your issues or pull requests there. And I will be there as your call.
Guard-rails is under FOLLOW YOUR HEART PUBLIC LICENSE version 1.