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.

Sign up for GitHub

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

Jump to bottom

Switching from config.json to .env #43

Closed

birajrai opened this issue Mar 3, 2025 · 1 comment

Assignees

Labels

Owner

birajrai commented Mar 3, 2025

Switching from `config.json` to `.env`

Is your feature request related to a problem?

Currently, the project uses config.json for configuration, making it harder to manage environment-specific settings and sensitive data.

Describe the solution you'd like

Use .env with the dotenv package to store configuration values securely and dynamically.

Describe alternatives you've considered

Keeping config.json but ignoring environment-specific versions.
Using a config.js file that loads values from environment variables.

Additional context

.env does not support nested objects, so some restructuring may be needed.
Values in .env are always strings, requiring manual type conversion.
dotenv package needs to be installed (npm install dotenv).

The text was updated successfully, but these errors were encountered:

birajrai added the enhancement label

birajrai self-assigned this

Owner Author

birajrai commented Mar 4, 2025

birajrai closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment