search

ranmocy / guard-rails

Guard-Rails is watching on your development servers as you wish!
http://ranmocy.github.com/guard-rails
MIT License
137 stars 25 forks source link

guard-rails doesn't longer start as daemon after upgrade from 0.2.3 to 0.3.4 #3

Closed swobspace closed 11 years ago

swobspace commented 11 years ago

I have upgraded to guard-rails 0.3.4, now guard-rails does not longer start as daemon. Foreground works, but daemon mode not.

0.3.1 seems also okay, so this bug may be introduced when switching to spawn instead of shell on starting rails server.

OS: Fedora 18 64-bit (Linux) Ruby: ruby 1.8.7 (2012-02-08 patchlevel 358) [x86_64-linux] Rails: 3.2.8 guard: 1.6.2 Guardfile (partial):

guard 'rails', :daemon => true, :force_run => true, :timeout => 10 do
  watch('Gemfile.lock')
  watch(%r{^(config/(initializers|environments)|lib)/.*})
  watch(%r{^config/*.rb})
end
´´´
ranmocy commented 11 years ago

Daemon mode does not works? Did you get the same notification of your OS and the same output in Guard console when you run rails in daemon and in foreground?

swobspace commented 11 years ago

0.3.1:

% bundle exec guard
11:32:45 - INFO - Guard uses Libnotify to send notifications.
11:32:46 - INFO - Bundle already up-to-date
11:32:46 - INFO - Guard::Rails will now restart your app on port 3000 using
development environment.
11:32:46 - INFO - Starting Rails...
=> Booting WEBrick
=> Rails 3.2.8 application starting in development on http://0.0.0.0:3000
11:32:50 - INFO - Rails started, pid 15424
11:32:50 - INFO - LiveReload 1.6 is waiting for a browser to connect.
11:32:50 - INFO - Starting Spork for RSpec
Using RSpec
Preloading Rails environment
Loading Spork.prefork block...
Rack::File headers parameter replaces cache_control after Rack 1.5.
Spork is ready and listening on 8989!
11:32:55 - INFO - Spork server for RSpec successfully started
11:32:55 - INFO - Guard::RSpec is running
11:32:55 - INFO - Guard is now watching at
'/home/wob/doc/Projects/beschlussdb'

0.3.4:

% bundle exec guard
11:34:27 - INFO - Guard uses Libnotify to send notifications.
11:34:27 - INFO - Bundle already up-to-date
11:34:28 - INFO - Guard::Rails will now restart your app on port 3000 using
development environment.
11:34:28 - INFO - Starting Rails...
11:34:28 - INFO - LiveReload 1.6 is waiting for a browser to connect.
11:34:28 - INFO - Starting Spork for RSpec
Using RSpec
Preloading Rails environment
Loading Spork.prefork block...
Rack::File headers parameter replaces cache_control after Rack 1.5.
Spork is ready and listening on 8989!
11:34:33 - INFO - Spork server for RSpec successfully started
11:34:33 - INFO - Guard::RSpec is running
11:34:33 - INFO - Guard is now watching at
'/home/wob/doc/Projects/beschlussdb'

The following lines are missing in 0.3.4 after "starting rails":

=> Booting WEBrick
=> Rails 3.2.8 application starting in development on http://0.0.0.0:3000
11:32:50 - INFO - Rails started, pid 15424

In foreground mode i get this three lines also with 0.3.4

ranmocy commented 11 years ago

I rollback to use sh -c to start Rails for avoiding platforms issue. Check out the v0.4.0. Thanks~

swobspace commented 11 years ago

v0.4.0 works for me. Thank you.