How to store Node.js deployment settings/configuration files?

manpreet Best Answer 2 years ago

_x000D_ I use a package.json for my packages and a config.js for my configuration, which looks like: var config = {}; config.twitter = {}; config.redis = {}; config.web = {}; config.default_stuff = ['red','green','blue','apple','yellow','orange','politics']; config.twitter.user_name = process.env.TWITTER_USER || 'username'; config.twitter.password= process.env.TWITTER_PASSWORD || 'password'; config.redis.uri = process.env.DUOSTACK_DB_REDIS; config.redis.host = 'hostname'; config.redis.port = 6379; config.web.port = process.env.WEB_PORT || 9980; module.exports = config; I load the config from my project: var config = require('./config'); and then I can access my things from config.db_host, config.db_port, etc... This lets me either use hardcoded parameters, or parameters stored in environmental variables if I don't want to store passwords in source control. I also generate a package.json and insert a dependencies section: "dependencies": { "cradle": "0.5.5", "jade": "0.10.4", "redis": "0.5.11", "socket.io": "0.6.16", "twitter-node": "0.0.2", "express": "2.2.0" } When I clone the project to my local machine, I run npm install to install the packages. More info on that here. The project is stored in GitHub, with remotes added for my production server.