Configure external chorus.services domain access

External Domain Configuration:
- Updated Docker Swarm for chorus.services domain (202.171.184.242)
- Configured dashboard.chorus.services for WHOOSH frontend
- Configured api.chorus.services for backend API
- Prepared www.chorus.services for marketing website (ready for submodule)

Traefik Configuration:
- SSL/TLS certificates via Let's Encrypt
- Domain redirects: chorus.services → www.chorus.services
- Proper CORS origins for external access
- Load balancing and high availability

Production Endpoints:
- Marketing Website: https://www.chorus.services (pending project)
- Dashboard: https://dashboard.chorus.services
- API: https://api.chorus.services
- Documentation: https://api.chorus.services/docs

Build System:
- Updated build scripts for website integration
- Registry image preparation: chorus-website:latest
- Management script updates for external domains

Ready for website project integration as git submodule when available.

README.md

@@ -22,11 +22,16 @@
 ```
 
 **Access Points:**
-- 🌐 **WHOOSH Dashboard**: http://localhost:3001
-- 📡 **API Documentation**: http://localhost:8087/docs  
+- 🌐 **Marketing Website**: https://www.chorus.services (production)
+- 🎛️ **Dashboard**: https://dashboard.chorus.services (production)
+- 📡 **API**: https://api.chorus.services (production)
 - 📊 **Grafana Monitoring**: http://localhost:3002 (admin/chorusadmin)
 - 🔍 **Prometheus Metrics**: http://localhost:9092
 
+**Local Development:**
+- Dashboard: http://localhost:3001
+- API Docs: http://localhost:8087/docs
+
 ## 🏗️ Architecture Overview
 
 CHORUS Services integrates five core components into a unified platform: