Add multi-server support and update docs

Introduce multi-server architecture documentation and reorganize README content. Top-level README now documents Core vs Remote server roles, links to local docs instead of wiki pages, and highlights Traefik/Sablier multi-server behavior. docker-compose/README.md was rewritten to be a template-style reference with single- and multi-server deployment guidance, Traefik label examples, and sablier usage; dockge README was moved into docker-compose/dockge/. docker-compose/core/README.md was updated to describe core responsibilities, shared CA artifacts, and startup order for multi-server deployments. Several obsolete/duplicated docs and action reports were removed and a new multi-server deployment doc was added to centralize on-demand/remote service guidance. Overall this cleans up legacy docs and documents the multi-server workflow and TLS/shared-CA requirements.

docs/post-setup.md

@@ -4,6 +4,8 @@ Congratulations! Your AI-powered homelab is now running. Here's what to do next.
 
 ## Access Your Services
 
+### Single Server Deployment
+
 - **Homepage**: `https://homepage.yourdomain.duckdns.org`
   - Great place to start exploring your services
   - After configuring your services, come back and add widgets with API keys (optional)
@@ -22,12 +24,35 @@ Congratulations! Your AI-powered homelab is now running. Here's what to do next.
 
 - **VS Code**: `https://code.yourdomain.duckdns.org`
    - Install GitHub Copilot Chat extension
-   - Open the AI-Homelab repository
+   - Open the EZ-Homelab repository
    - Use AI assistance for:
       - Adding new services
       - Configuring Traefik routing
       - Managing Docker stacks
 
+### Multi-Server Deployment
+
+If you deployed across multiple servers:
+
+**Core Server Services** (accessed from anywhere):
+- All services above (Homepage, Dockge, Authelia, Traefik, code-server)
+- Access these through your domain: `service.yourdomain.duckdns.org`
+
+**Remote Server Services** (accessed through core):
+- Remote services automatically routed through core Traefik
+- Example: `https://sonarr.yourdomain.duckdns.org` → Core → Remote Server
+- SSO protection applied by core Authelia
+
+**Direct Local Access** (on remote server network):
+- Services also accessible via local IP: `http://192.168.1.100:8989`
+- Useful for troubleshooting or local management
+- No SSO protection on local access
+
+**Management Tips:**
+- Use core Dockge to manage all servers (if configured)
+- Each server has its own local Traefik/Sablier for container management
+- All services appear under unified domain through core routing
+
 ## Monitoring Services
 
 - Use Dockge to easily view live container logs