Nest: What's the right way to holding configuration for multi-env?

[janckerchen]

hold env config like: ip, port, db, ....

config/
dev.ts
prod.ts
test.ts

I have multi modules in project, should I create a shared module to hold env config?

[rmvermeulen]

If I understand correctly, maybe this can help https://www.npmjs.com/package/config

[cojack]

@janckerchen Im handling this by this example: https://github.com/cojack/ts-config

[darioxtx]

I'm using https://github.com/mozilla/node-convict

[kamilmysliwiec]

Additionally, you can do it in more nest-way, using custom providers. Example:

provide: ConfigService,
useClass: process.env.NODE_ENV === 'development' 
     ? DevelopmentConfigService 
     : ProductionConfigService

where ConfigService is an abstract class and both DevelopmentConfigService and ProductionConfigService extends ConfigService.

[janckerchen]

thx @kamilmysliwiec . I found there are three ways to spread config to multi modules.

1. pass config to anymodule.forRoot(config). it's a static way, config is passed before module creation and some provider factories will consume the config data.
2. build ConfigService like @kamilmysliwiec mentioned above. config is injected to component constructor, that's mean config is passed before component creation.
3. pass config to AnyService.Init(config) in module's constructor, because any component belongs to the module can be inject to module's constructor. At this time, component has been created.

I switched from rails, I expect proper nest-way to manage config.

[trainerbill]

Are there plans to build @kamilmysliwiec recommendation into the framework?

[neilime]

And what about https://github.com/nestjs-community/nestjs-config ?

[maximpyshko]

Try https://github.com/maximpyshko/neconfig

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.