User customized config

[andretw]

I'm using this on Heroku. I just need to write a config_heroku.json and write "web: node index.js -c config_heroku.json" in Procfile. And the variables will be overridden by config_heroku.json.
Thus, I don't need to set env variables or change any other stuff any more.
I can test my cody-cms on localhost or heroku easily.

[ticup]

Great, Thanks for the pull request.

Just for homogeneity, I suggest we do it like this and let the environment variables have the biggest importance.

If you agree, could you be so kind to adjust accordingly and resubmit the pull request?

Thanks!

// setup the config. Order of importance: config.json < -c command line config < environment values
// 1. load default config
cody.config = require('./config');
cody.config.controllers = require("./controllers/");

// 2. if -c exists, overwrite customized config values
if(process.argv.indexOf("-c") != -1){
    var extraConfigFilePath = process.argv[process.argv.indexOf("-c") + 1];
    var obj = JSON.parse(fs.readFileSync(extraConfigFilePath, 'utf8'));
    Object.keys(cody.config).forEach(function (name) {
        cody.config[name] = obj[name] || cody.config[name];
    });
}

// 3. overwrite environment variable values
Object.keys(cody.config).forEach(function (name) {
  cody.config[name] = process.env[name] || cody.config[name];
});

[jcoppieters]

thanks mate !

wou het eigenlijk vragen aan jou, want moet eerst nog 40 examens verbeteren (is wel nodejs, dus dat valt mee, maar toch)

J.

[andretw]

@ticup yes, to use global env is more reasonable. I've re-ordered the loading steps. Thanks for your advice. 😄

@jcoppieters sorry, I don't understand Dutch. 😭

[ticup]

Awesome @andretw!
Your changes are now in v3.2.5, which is also pushed to npm.
Congratz and thanks for being the first outside contributor ;)