Problem
The project currently uses hardcoded configuration values (such as API URLs and settings) within the codebase.
This leads to:
- Security risks if sensitive values are exposed
- Difficulty in managing different environments (development, production)
- Reduced flexibility and maintainability
Expected Behavior
- Configuration values should be managed using environment variables
- Sensitive data should not be hardcoded in the source code
- The project should support easy setup across environments
Proposed Solution
- Move configuration values to a
.env file
- Use a library like
python-dotenv to load environment variables
- Add a
.env.example file for reference
- Update backend code to read values from environment variables
- Update README with setup instructions
Impact
- Improves security and maintainability
- Makes the project easier to configure and deploy
- Follows industry best practices
Additional Context
I would like to work on this issue and submit a PR.
Problem
The project currently uses hardcoded configuration values (such as API URLs and settings) within the codebase.
This leads to:
Expected Behavior
Proposed Solution
.envfilepython-dotenvto load environment variables.env.examplefile for referenceImpact
Additional Context
I would like to work on this issue and submit a PR.