ember-cli-rails 0.3.1 → 0.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ed4f0d180cccc933077229419ad7bd0044b8ab48
-  data.tar.gz: 5e0a09712c67f5e53db7f6a3a63a7acfe934e913
+  metadata.gz: 05518de12c5efde4161912094e2e19430fbc9f16
+  data.tar.gz: 35f500e2105b1714945c310d9bf353c67f0c5c55
 SHA512:
-  metadata.gz: 93353ebfdd5924d58cfc74bd3731e04cb663fa82243c74eb76456fd5fda97ea9da05dec933af1fdc022ec46e398dda4e4634778cf6de6d7aa1bbf76afb54ff74
-  data.tar.gz: 66fdcb460d14ee24138825ac855567039fe9f72bcf33d13840623db59329983166c9a296b5d185b056e69670905f23457a5602a94b0fb4a9fa73e497d2ad51a7
+  metadata.gz: b7f04732af5f5e38999ec89dab249ee1b3451d48774984c6c56ad804c60fade657d6f78131905d8d35a84e9b1db846a1a56e95b333b93c8a2121ccc8b2cab205
+  data.tar.gz: 3fc97b6814f3ef9989f07a2bda72604ab4b1b0c3bee7b1c5e3d651a91c85a8f45e1859a6aadbbf38aa176fe058ca25bf0a3ab6595003e75f71485d2e06c80922

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+0.3.2
+-----
+
+* Inject `RAILS_ENV` into `ember build` process [#168][https://github.com/rwz/ember-cli-rails/pull/168]
+* Explicitly register view helpers [#148](https://github.com/rwz/ember-cli-rails/pull/148)
+
 0.3.1
 -----
 

data/README.md

@@ -207,7 +207,7 @@ In order to deploy EmberCLI Rails app to Heroku:
 First, enable Heroku Multi Buildpack by running the following command:
 
 ```sh
-heroku config:add BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-multi
+heroku buildpacks:set https://github.com/heroku/heroku-buildpack-multi
 ```
 
 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
 `config.use_ember_live_recompilation` flags in the environment-specific config
 file.
 
+### `RAILS_ENV`
+
+While being managed by EmberCLI Rails, EmberCLI process will have
+access to the `RAILS_ENV` environment variable. This can be helpful to detect
+the Rails environment from within the EmberCLI process.
+
+This can be useful to determine whether or not EmberCLI is running in its own
+standalone process or being managed by Rails.
+
+For example, to enable [ember-cli-mirage][ember-cli-mirage] API responses in
+`development` while being run outside of Rails (while run by `ember serve`),
+check for the absence of the `RAILS_ENV` environment variable:
+
+```js
+// config/environment.js
+if (environment === 'development') {
+  ENV['ember-cli-mirage'] = {
+    enabled: typeof process.env.RAILS_ENV === 'undefined',
+  }
+}
+```
+
+`RAILS_ENV` will be absent in production builds.
+
+[ember-cli-mirage]: http://ember-cli-mirage.com/docs/latest/
+
 #### Ember Dependencies
 
 Ember has several dependencies. Some of these dependencies might already be

data/lib/ember-cli/app.rb

@@ -231,6 +231,7 @@ module EmberCLI
 
     def env_hash
       ENV.clone.tap do |vars|
+        vars.store "RAILS_ENV", Rails.env
         vars.store "DISABLE_FINGERPRINTING", "true"
         vars.store "EXCLUDE_EMBER_ASSETS", excluded_ember_deps
         vars.store "BUNDLE_GEMFILE", gemfile_path.to_s if gemfile_path.exist?

data/lib/ember-cli/engine.rb

@@ -9,5 +9,11 @@ module EmberCLI
     initializer "ember-cli-rails.enable" do
       EmberCLI.enable! unless EmberCLI.skip?
     end
+
+    initializer "ember-cli-rails.helpers" do
+      config.to_prepare do
+        ActionController::Base.helper EmberRailsHelper
+      end
+    end
   end
 end

data/lib/ember-cli/version.rb

@@ -1,3 +1,3 @@
 module EmberCLI
-  VERSION = "0.3.1".freeze
+  VERSION = "0.3.2".freeze
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ember-cli-rails
 version: !ruby/object:Gem::Version
-  version: 0.3.1
+  version: 0.3.2
 platform: ruby
 authors:
 - Pavel Pravosud
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-04-06 00:00:00.000000000 Z
+date: 2015-06-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties