Specify an ENV configuration as a task, e.g.
grunt.registerTask('dev', ['env:dev', 'lint', 'server', 'watch']);
grunt.registerTask('build', ['env:build', 'lint', 'other:build:tasks']);
Install this grunt plugin next to your project's grunt.js gruntfile with: npm install grunt-env
Then add this line to your project's grunt.js
gruntfile:
grunt.loadNpmTasks('grunt-env');
env : {
options : {
//Shared Options Hash
},
dev : {
NODE_ENV : 'development',
DEST : 'temp'
},
build : {
NODE_ENV : 'production',
DEST : 'dist'
}
}
You can specify environment values in INI or JSON style and load them via the src option.
env : {
dev : {
src : "dev.json"
},
heroku : {
src : ".env"
}
}
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using grunt.
- 0.4.0 Removed automatic parse, added ability to add ini or json style
src
files - 0.3.0 Automatically parses .env files now
- 0.2.1 fixed npm install
- 0.2.0 grunt 0.4.0 support, simplified
- 0.1.0 Initial release
Copyright (c) 2012 OneHealth Solutions, Inc Licensed under the Apache 2.0 license.
Jarrod Overson