LO-068 [Easy]: Add Django Settings Validation on Startup

[Kuldeeep18]

Description

If LeadOrbit is deployed without configuring essential environment variables (e.g. missing GEMINI_API_KEY, GOOGLE_CLIENT_ID or database host credentials), the server starts but crashes dynamically when executing features. We need validation checks on startup.

User & Contributor Value

• Contributors: Django settings loading lifecycle, handling early exceptions, and environment testing.
• Users: Prevents deploying misconfigured applications to production.

Code Locations

• backend/backend/wsgi.py
• backend/backend/asgi.py

Implementation Guide

1. In wsgi.py and asgi.py (after django setup), check that crucial settings like GEMINI_API_KEY are not empty.
2. If missing, write a clear, bold warning message to stdout detailing which environment variables are missing.

[manikanta-tamminana]

Hi @Kuldeep18,

I would like to work on this issue under GSSoC.

My implementation plan is:

• Add startup validation checks in both wsgi.py and asgi.py after Django initialization.
• Verify the presence of critical environment variables such as GEMINI_API_KEY, GOOGLE_CLIENT_ID, database credentials, and other required configuration values.
• Generate clear, readable warning messages identifying any missing variables and explaining their impact.
• Ensure the validation runs during application startup so deployment issues are detected early rather than during runtime.
• Keep the validation logic maintainable and easy to extend as new environment variables are introduced.

This enhancement will improve deployment reliability by helping developers identify configuration issues immediately and preventing unexpected runtime failures. Could you please assign this issue to me?

Thank you! 🚀