Configuration chaining about kraken-js

[jeffharrell]

We're managing a settings which only apply to a specific setting by exporting them to the environment before starting the application. nconf consumes env() and / or you can then access these using process.env.

Are you looking for something above this level of detail or is there a need to composite / force rank the settings?

[cliffano]

I was thinking more of a composite / force rank the config files.
But I think this probably falls into the "too much for Kraken" category as discussed in issue #23 .

Closing this issue.

[sergej-brazdeikis]

@cliffano,

if you look inside of kraken-js source it is already supported: https://github.com/paypal/kraken-js/blob/master/lib/util/configutil.js#L93

You can create files environment based config files:

• app-production.js
• app-staging.js
• app-test.js
• app-development.js

with NODE_ENV=test kraken-js will load app.jsand then extend it with app-test.js

Hope this answers your question

[ericglasser]

@sjevs I am trying to do something similar and ran into an issue with needing multiple development environments. I need a local and a development one, and no matter what I set the app-local.js to it inherits production settings for file paths. Basically it is pulling from the .build directory on the front end.