Closed mmacedo closed 12 years ago
If for any reason RAILS_ENV was set to test this command will start a Rails server with test environment:
rails s -e development
But this one will start with development environment:
RAILS_ENV=development rails s
I am not sure who is at fault here, but this ensures guard-rails will always use the environment specified by the environment option.
Works for me. Thanks!
If for any reason RAILS_ENV was set to test this command will start a Rails server with test environment:
But this one will start with development environment:
I am not sure who is at fault here, but this ensures guard-rails will always use the environment specified by the environment option.