github-migration
/
guard-rails
1
0
Fork 0
Code Issues 6 Pull Requests 2 Packages Projects Releases Wiki Activity

Ensure specified environment is used #18

Merged
mmacedo merged 1 commits from environment into master 2012-07-09 12:48:29 +00:00
Conversation 1 Commits 1 Files Changed 1 +1 -1
mmacedo commented 2012-07-08 09:38:19 +00:00 (Migrated from github.com)
Copy Link

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.

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.
johnbintz commented 2012-07-09 12:48:36 +00:00 (Migrated from github.com)
Copy Link

Works for me. Thanks!

Works for me. Thanks!
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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#18
No description provided.
Delete Branch "environment"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?