Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nested keys are not being accepted by nconf #336

Open
Redsandro opened this issue Oct 11, 2019 · 0 comments
Open

Nested keys are not being accepted by nconf #336

Redsandro opened this issue Oct 11, 2019 · 0 comments

Comments

@Redsandro
Copy link

I have this confusing situation where nested keys from my .env file are ignored by nconf when using certain Docker containers, e.g.: FROM node:8.

The exact same thing works fine with different containers, e.g.: FROM node:8-alpine

What causes this inconsistency? Can I remedy this within node? Or is the only solution to this problem to use a different separator?

If the latter is the case, I think using colon (:) as the default is a bad idea, and the default should be changed to something that works on all containers.

PS - I have observed the same behavior using a dash/minus symbol (-). It is accepted by nconf on node:8-alpine but not on node:8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant