docs: update edge case for ConfigModule

[PhearZero]

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines: https://github.com/nestjs/docs.nestjs.com/blob/master/CONTRIBUTING.md

PR Type

What kind of change does this PR introduce?

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [x] Docs
• [ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Other information

[kamilmysliwiec]

I wonder if we should use --env-file flag in this case instead

[micalevisk]

yeah, having to import dotenv ourselves seems odd.

[kamilmysliwiec]

To make things simpler, we might expose the --env-file flag on the nest start command and just pass it down to node (instead of forcing everyone to use --exec etc)

[PhearZero]

It's only a few more months before Node 18 hits end of life, feel free to close the ticket in favor of a --env-file pass-through

[kamilmysliwiec]

https://github.com/nestjs/nest-cli/pull/2818