Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat non {test,development} envs as production #366

Merged
merged 1 commit into from
Dec 20, 2015

Conversation

seanpdoyle
Copy link
Contributor

Closes #361.

When the Rails environment is neither test nor development (two
environments handled by EmberCLI out-of-the-box
), treat
it as production, unless an EMBER_ENV is specified.

Closes [#361].

When the Rails environment is neither `test` nor `development` ([two
environments handled by EmberCLI out-of-the-box][ember-cli-env]), treat
it as `production`, unless an `EMBER_ENV` is specified.

[#361]: #361
[ember-cli-env]: http://ember-cli.com/user-guide/#Environments
@seanpdoyle seanpdoyle merged commit 94b7dd6 into master Dec 20, 2015
@seanpdoyle seanpdoyle deleted the current-environment branch December 20, 2015 01:49
## `EMBER_ENV`

If set on the environment, the value of `EMBER_ENV` will be passed to the
`ember` process as the value of the `--environment` flag.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit confused on this. Doesn't this code always force the environment passed to --environment to be either development or production?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@seanpdoyle Did you see the above comment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants