ember-cli-rails 0.3.1 → 0.3.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +6 -0
- data/README.md +27 -1
- data/lib/ember-cli/app.rb +1 -0
- data/lib/ember-cli/engine.rb +6 -0
- data/lib/ember-cli/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 05518de12c5efde4161912094e2e19430fbc9f16
|
4
|
+
data.tar.gz: 35f500e2105b1714945c310d9bf353c67f0c5c55
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b7f04732af5f5e38999ec89dab249ee1b3451d48774984c6c56ad804c60fade657d6f78131905d8d35a84e9b1db846a1a56e95b333b93c8a2121ccc8b2cab205
|
7
|
+
data.tar.gz: 3fc97b6814f3ef9989f07a2bda72604ab4b1b0c3bee7b1c5e3d651a91c85a8f45e1859a6aadbbf38aa176fe058ca25bf0a3ab6595003e75f71485d2e06c80922
|
data/CHANGELOG.md
CHANGED
data/README.md
CHANGED
@@ -207,7 +207,7 @@ In order to deploy EmberCLI Rails app to Heroku:
|
|
207
207
|
First, enable Heroku Multi Buildpack by running the following command:
|
208
208
|
|
209
209
|
```sh
|
210
|
-
heroku
|
210
|
+
heroku buildpacks:set https://github.com/heroku/heroku-buildpack-multi
|
211
211
|
```
|
212
212
|
|
213
213
|
Next, specify which buildpacks to use by creating a `.buildpacks` file in the project root containing:
|
@@ -264,6 +264,32 @@ environment, you can manually set the `config.use_ember_middleware` and
|
|
264
264
|
`config.use_ember_live_recompilation` flags in the environment-specific config
|
265
265
|
file.
|
266
266
|
|
267
|
+
### `RAILS_ENV`
|
268
|
+
|
269
|
+
While being managed by EmberCLI Rails, EmberCLI process will have
|
270
|
+
access to the `RAILS_ENV` environment variable. This can be helpful to detect
|
271
|
+
the Rails environment from within the EmberCLI process.
|
272
|
+
|
273
|
+
This can be useful to determine whether or not EmberCLI is running in its own
|
274
|
+
standalone process or being managed by Rails.
|
275
|
+
|
276
|
+
For example, to enable [ember-cli-mirage][ember-cli-mirage] API responses in
|
277
|
+
`development` while being run outside of Rails (while run by `ember serve`),
|
278
|
+
check for the absence of the `RAILS_ENV` environment variable:
|
279
|
+
|
280
|
+
```js
|
281
|
+
// config/environment.js
|
282
|
+
if (environment === 'development') {
|
283
|
+
ENV['ember-cli-mirage'] = {
|
284
|
+
enabled: typeof process.env.RAILS_ENV === 'undefined',
|
285
|
+
}
|
286
|
+
}
|
287
|
+
```
|
288
|
+
|
289
|
+
`RAILS_ENV` will be absent in production builds.
|
290
|
+
|
291
|
+
[ember-cli-mirage]: http://ember-cli-mirage.com/docs/latest/
|
292
|
+
|
267
293
|
#### Ember Dependencies
|
268
294
|
|
269
295
|
Ember has several dependencies. Some of these dependencies might already be
|
data/lib/ember-cli/app.rb
CHANGED
@@ -231,6 +231,7 @@ module EmberCLI
|
|
231
231
|
|
232
232
|
def env_hash
|
233
233
|
ENV.clone.tap do |vars|
|
234
|
+
vars.store "RAILS_ENV", Rails.env
|
234
235
|
vars.store "DISABLE_FINGERPRINTING", "true"
|
235
236
|
vars.store "EXCLUDE_EMBER_ASSETS", excluded_ember_deps
|
236
237
|
vars.store "BUNDLE_GEMFILE", gemfile_path.to_s if gemfile_path.exist?
|
data/lib/ember-cli/engine.rb
CHANGED
data/lib/ember-cli/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: ember-cli-rails
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.3.
|
4
|
+
version: 0.3.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Pavel Pravosud
|
@@ -10,7 +10,7 @@ authors:
|
|
10
10
|
autorequire:
|
11
11
|
bindir: bin
|
12
12
|
cert_chain: []
|
13
|
-
date: 2015-04
|
13
|
+
date: 2015-06-04 00:00:00.000000000 Z
|
14
14
|
dependencies:
|
15
15
|
- !ruby/object:Gem::Dependency
|
16
16
|
name: railties
|