Is your feature request related to a problem? Please describe.
Currently, backend utility functions are scattered across different files and locations. This results in code duplication and complexity in maintenance.
Describe the solution you'd like
Refactor all shared backend utility functions into a dedicated folder structure (/backend/utils/ or similar). Organize the utilities in a way that supports easier import, improved maintainability, and better clarity.
Also replace all os.getenv calls with a centralized config.py using configparser, so all configuration variables are managed in one place rather than scattered across the codebase.
Describe alternatives you've considered
- Keeping utility functions where they are but documenting their use more clearly.
- Using a single utilities file instead of a structured directory.
Additional context
This change will benefit future refactoring, testing, and collaborative development across backend modules.
Is your feature request related to a problem? Please describe.
Currently, backend utility functions are scattered across different files and locations. This results in code duplication and complexity in maintenance.
Describe the solution you'd like
Refactor all shared backend utility functions into a dedicated folder structure (
/backend/utils/or similar). Organize the utilities in a way that supports easier import, improved maintainability, and better clarity.Also replace all os.getenv calls with a centralized config.py using configparser, so all configuration variables are managed in one place rather than scattered across the codebase.
Describe alternatives you've considered
Additional context
This change will benefit future refactoring, testing, and collaborative development across backend modules.