- Enable DEBUG=True to see detailed error messages on failing pages
- Disable SECURE_SSL_REDIRECT to allow HTTP access while troubleshooting
- Add both HTTP and HTTPS to CSRF_TRUSTED_ORIGINS
This will help identify why other pages show 500 errors.
Once issues are fixed, we'll re-enable production settings.
- Add docker-compose.dokploy-external-db.yml that matches quantum-digital exactly
- Uses external DATABASE_URL only (no db container)
- Fix docker-compose.dokploy-simple.yml to include database container with proper networking
Choose one approach:
- dokploy-external-db.yml: Use with external database (Neon, Supabase, etc.)
- dokploy-simple.yml: Use with Docker PostgreSQL container
The error 'could not translate host name db' is fixed in both versions.
Based on analysis of successfully deployed project:
- Create docker-compose.dokploy-simple.yml with ports instead of expose
- Remove complex Traefik labels (let Dokploy handle routing via Domain UI)
- Hardcode environment variables in compose file
- Run migrations in the command directly
- Add Dockerfile.simple following their working multi-stage pattern
- Includes Tailwind build and health check
Use docker-compose.dokploy-simple.yml and configure domain via Dokploy UI
