Clarify environment variable and .env configuration strategy #39
Description
Observation
The project partially supports environment variables:
- PORT can be overridden via environment variable
- python-dotenv is installed
- load_dotenv() logic exists but is commented out
However, the intended configuration strategy is unclear:
- Should .env be used for local development?
- Are environment variables expected in production only?
- Is dotenv intentionally disabled?
Proposal
Clarify the intended configuration approach by:
- Documenting environment variable usage in README
- Either enabling load_dotenv() for local dev
- Or removing dotenv dependency if not intended to be used
Benefit
- Clear configuration strategy
- Less contributor confusion
- Cleaner architecture direction