3 Commits

Author	SHA1	Message	Date
amitrana01	876ce06634	🧹 MAJOR CLEANUP: Remove all debugging files and confusion ... ✅ CLEANED FILES: - Removed 5 duplicate docker-compose files → kept 1 working docker-compose.dokploy.yml - Deleted debugging files: debug_settings.py, test-docker-build.sh, cookies.txt, entrypoint.sh - Removed redundant docs: DOKPLOY.md, DEPLOYMENT.md, QUICKSTART.md, Dockerfile.simple - Fixed all file references to use docker-compose.dokploy.yml consistently 📚 CLEAN DOCUMENTATION STRUCTURE: - README.md: Overview with quick links to deployment guides - QUICK_DEPLOY.md: 3-step deployment guide (zero code changes needed) - DEPLOYMENT_CHECKLIST.md: Complete troubleshooting reference - WARP.md: Developer/agent guidance 🎯 RESULT: - Clean, confusion-free project structure - Single source of truth for deployment - Zero hardcoded values - everything uses environment variables - Clone-and-deploy ready with minimal setup The project is now production-ready and maintainable! 🚀	2025-09-11 19:19:40 +05:30
amitrana01	7a47ca4058	Fix django_site relation error by adding Site configuration ... - Add configure_site management command to create Django Site object - Configure site domain as dt.netcoptech.com during startup (like quantum-digital) - Update both compose files to run configure_site after migrations - This fixes the 'relation django_site does not exist' error on /accounts/login/ Django Allauth requires a Site object to work properly.	2025-09-11 18:39:00 +05:30
amitrana01	23f9778964	Add debugging for environment variables and Django settings ... - Fix production.py settings to properly read environment variables with defaults - Add debug_settings management command to troubleshoot environment variable issues - Add debugging output to entrypoint.sh to see what settings are loaded - This will help identify why ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS may not be working	2025-09-11 18:04:23 +05:30