Guard restart Rails in test mode not in development #20

New Issue

2012-08-13T21:08:31Z

anton-yordanov commented

2012-08-13 21:08:31 +00:00

(Migrated from github.com)

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

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

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: github-migration/guard-rails#20