johnbintz/guard-rails

No longer maintained. Latest version is at https://github.com/ranmocy/guard-rails

guard-rails's Issues

add other server option

tehpeh@372e2cd

Do not restart Rails when changing config/locales

Just a thought while I was editing some small locale changes that reloading the whole of rails might be overkill for lazy loadable locale changes.

Forcibly close the process holding open the socket you want if it's open

lsof -P | grep "*:#{port} " will do it on Mac OS X. Have a new guard option, :force_run, that tried to kill the associated PID if it's found.

Rails server should be (re)started on reload?

Hi John,

Just thinking that the rails server should be started and restarted on guard's reload command rather than run_all?

This would mean when you reload guard with r+enter it will restart the server, but just hitting enter will not do anything.

What do you think?

For me that makes sense if I also run rspec and cucumber in my guardfile, so enter runs all the tests, and r+enter reloads the server and spork.

How would one use bundle exec?

How would one use bundle exec before the server command?

uninitialized constant Guard::Dsl::Rails,

When I put this code in a Guardfile

Rails.root.join('spec/javascripts'),

It occurs error uninitialized constant Guard::Dsl::Rails.

Is any other way to point the root directory?

The dependency on version is incompatible with paper_trails version class

All of a sudden (after upgrading guard-rails) to latest version we get the following errors

Started GET "/" for 127.0.0.1 at 2013-02-25 11:25:13 +0100
Processing by PagesController#show as HTML
  Site Load (0.3ms)  SELECT "sites".* FROM "sites" WHERE "sites"."subdomain" = 'dev' LIMIT 1
  Page Load (0.3ms)  SELECT "pages".* FROM "pages" WHERE "pages"."site_id" = 1 AND "pages"."url" = '' LIMIT 1
  Version Load (0.4ms)  SELECT "versions".* FROM "versions" WHERE "versions"."item_id" = 1 AND "versions"."item_type" = 'Page' AND "versions"."published_at" = '2013-02-21 17:30:23.241998' ORDER BY created_at ASC, id ASC LIMIT 1
Completed 500 Internal Server Error in 6ms

NoMethodError (protected method `[]' called for "":Version):
  app/models/concerns/versionable.rb:69:in `published_version'
  app/controllers/pages_controller.rb:9:in `show'
  app/controllers/application_controller.rb:172:in `set_logger_site_id'
  app/controllers/application_controller.rb:178:in `set_logger_username'

Log output interrupts test output

It'd be nice if you could have an option to suppress server log output and just tail the development log in another terminal session.

Debugger do not work properly

As in topic, debugger do not work properly with guard, it means it stops for a short while and then render rest of website, so you can not type anything in debugger.

Some info:

• Test app can be found here: https://github.com/kiela/guard-rails-myapp
• Logs from setup app can be found here: https://github.com/kiela/guard-rails-myapp/blob/master/install.log

Used:

• rvm 1.6.10
• ruby 1.9.2-p180
• rails 3.2.1

The next release

Is there any chance to make a release from the current commits in the master? I would sure like some of them, like the one with SIGINT, it's taking 30 seconds for my server to restart.

Guard restart Rails in test mode not in development

Guard::Rails will now restart your app on port 3000 using thin and development environment.
=> Booting Thin
=> Rails 3.2.6 application starting in test on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server

Thin web server (v1.4.1 codename Chromeo)
Maximum connections set to 1024
Listening on 0.0.0.0:3000, CTRL+C to stop

my guard-rails configuration:

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

it doesn't support rails 2.*

will this be possible?

Does not work with mountable engines

This guard does currently not work with mountable engines due to the lack of rails s in the engine root. It should detect that its being run in a mountable engine and use test/dummy/script/rails s instead.

Doesn't work well with RSpec/guard-rspec

When the server is restarted via guard-rails, the specs fail with the following error:

Running: spec/routing spec/controllers/kong/clients_controller_spec.rb
/Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/configuration.rb:780:in `load': cannot load such file -- /Users/aziz/Sandbox/ruby/rails/agile_baboon/spec/routing (LoadError)
    from /Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/configuration.rb:780:in `block in load_spec_files'
    from /Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/configuration.rb:780:in `map'
    from /Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/configuration.rb:780:in `load_spec_files'
    from /Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/command_line.rb:22:in `run'
    from /Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/runner.rb:69:in `run'
    from /Users/aziz/.rvm/gems/ruby-1.9.3-p194@rails_agile_baboon/gems/rspec-core-2.11.1/lib/rspec/core/runner.rb:8:in `block in autorun'

Depreciation Warning run_on_change

This is really about about guard/guard-rails
There are depreciation warnings about run_on_change. I noticed you already updated this gem (johnbintz/guard-rails); can you update the guard/guard-rails gem as well? I couldn't submit an issue there. Is that gem unsupported now?

DEPRECATION: Starting with Guard v1.1 the use of the 'run_on_change' method in the 'Guard::Rails' guard is deprecated.
Please consider replacing that method-call with 'run_on_changes' if the type of change
is not important for your usecase or using either 'run_on_modifications' or 'run_on_additions'
based on the type of the changes you want to handle.
For more information on how to update existing guards, please head over to:
https://github.com/guard/guard/wiki/Upgrade-guide-for-existing-guards-to-Guard-v1.1

Ensure Guard returns a boolean status

For now, have it always return true.

foreman support

What is an usual way to run apps using foreman ?