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.
This commit is contained in:
52
WEBSITE_INTEGRATION.md
Normal file
52
WEBSITE_INTEGRATION.md
Normal file
@@ -0,0 +1,52 @@
|
||||
# Website Integration - Ready for Submodule Addition
|
||||
|
||||
## Status: Prepared ✅
|
||||
|
||||
The CHORUS Services platform is fully configured for the www.chorus.services website integration. All configuration is ready for when the website project is created.
|
||||
|
||||
## Configuration Complete
|
||||
|
||||
### Docker Swarm Configuration
|
||||
- `docker-compose.swarm.yml` includes `chorus-website` service
|
||||
- Traefik labels configured for `www.chorus.services` and `chorus.services`
|
||||
- Domain redirect: `chorus.services` → `www.chorus.services`
|
||||
- SSL/TLS certificates via Let's Encrypt
|
||||
- Registry image: `registry.home.deepblack.cloud/tony/chorus-website:latest`
|
||||
|
||||
### Build Scripts
|
||||
- `build-and-push.sh` includes website build support
|
||||
- Individual build command: `./build-and-push.sh website`
|
||||
- Integrated with unified build: `./chorus.sh build`
|
||||
|
||||
### Management Integration
|
||||
- `./chorus.sh deploy` includes website in production deployment
|
||||
- Production endpoints configured and documented
|
||||
|
||||
## Next Steps (When Website Project is Ready)
|
||||
|
||||
1. **Add Git Submodule:**
|
||||
```bash
|
||||
git submodule add <website-repo-url> modules/website
|
||||
```
|
||||
|
||||
2. **Build and Deploy:**
|
||||
```bash
|
||||
./chorus.sh build # Includes website
|
||||
./chorus.sh deploy # Deploys to production
|
||||
```
|
||||
|
||||
3. **Access Points:**
|
||||
- **Marketing**: https://www.chorus.services
|
||||
- **Dashboard**: https://dashboard.chorus.services
|
||||
- **API**: https://api.chorus.services
|
||||
|
||||
## Domain Configuration ✅
|
||||
|
||||
External domains configured with DNS pointing to 202.171.184.242:
|
||||
- `chorus.services` (redirects to www)
|
||||
- `www.chorus.services` (marketing website)
|
||||
- `dashboard.chorus.services` (WHOOSH dashboard)
|
||||
- `api.chorus.services` (API endpoints)
|
||||
- `*.chorus.services` (wildcard for future services)
|
||||
|
||||
All Traefik labels and routing ready for production deployment.
|
||||
Reference in New Issue
Block a user