This is a fork of fivetanley/ember-cli-dotenv with PR#6 by github.com/gniquil that I created just to ease my deployment via NPM. All credit goes to the original authors. This repo is not intended for production use, just learning from it.
npm install --save-dev ember-cli-dotenv
This addon allows you to write environment variables in a .env
file and
expose them to your Ember app through the built-in config/environment.js
that you can import in your app. For example, you might be building an
app with Dropbox and don’t want to check your key into the repo. Put a .env
file in the root of your repository:
DROPBOX_KEY=YOURKEYGOESHERE
Next, put some configuration in your Brocfile. Starting in 0.2.0, client side keys must be explicitly allowed:
// Brocfile.js
var app = new EmberApp({
dotEnv: {
clientAllowedKeys: ['DROPBOX_KEY']
}
});
// pre-generated config from ember-cli
module.exports = app.toTree();
All keys in .env
are currently injected into node’s process.env
.
These will be available in your config/environment.js
file:
// config/environment.js
module.exports = function(environment){
return {
MY_OTHER_KEY: process.env.MY_OTHER_KEY
}
};
You can then use the node process environment variables in other ember-cli-addons, such as express middleware or other servers/tasks.
Security: environment variables in config/environment.js
are never filtered
unlike using .env
and clientAllowedKeys
. Remember to use the environment
variable passed into your config function to filter out secrets for production
usage.
then, you can access the environment variables anywhere in your app like you usually would.
import ENV from "my-app/config/environment";
console.log(ENV.DROPBOX_KEY); // logs YOURKEYGOESHERE
You can read more about dotenv files on their dotenv repository.
All the work is done by ember-cli and dotenv. Thanks ember-cli team and dotenv authors and maintainers! Thanks Brandon Keepers for the original dotenv ruby implementation.
Sometime people may want to use different .env
file than the one in project root.
This can be configured as below:
// Brocfile.js
var app = new EmberApp({
dotEnv: {
clientAllowedKeys: ['DROPBOX_KEY'],
path: './path/to/.env'
}
});
// pre-generated config from ember-cli
module.exports = app.toTree();
In addition, you may also customize for different environments:
// Brocfile.js
var app = new EmberApp({
dotEnv: {
clientAllowedKeys: ['DROPBOX_KEY'],
path: {
development: './path/to/.env',
test: './path/to/.env.test',
production: './path/to/.env.production'
}
}
});
// pre-generated config from ember-cli
module.exports = app.toTree();
With the above, if you run ember build --environment production
, the file
.env.production
will be used instead.
git clone
this repositorynpm install
bower install
ember server
- Visit your app at http://localhost:4200.
ember test
ember test --server
ember build
For more information on using ember-cli, visit http://www.ember-cli.com/.