Files

kelinfoxy 5cbb106160 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.

2026-02-05 22:30:52 -05:00

4.8 KiB

Raw Blame History

Multi-Server Deployment with On-Demand Services

Overview

This guide explains the current multi-server architecture where:

Core Server: Handles external traffic (ports 80/443); runs DuckDNS, Traefik (multi-provider), Authelia
Remote Servers: Run their own Traefik (local-only) and Sablier (local containers)
No Docker API: Servers communicate via HTTP/HTTPS; no TLS Docker API connections needed
Independent Management: Each server manages its own containers with lazy loading

Note

: This document describes the current simplified architecture. For the legacy centralized Sablier approach, see the git history.

Architecture Diagram

┌─────────────────────────────────────────────────────────────────┐
│                         CORE SERVER                              │
│  ┌────────────┐  ┌──────────┐  ┌──────────┐  ┌──────────────┐ │
│  │  DuckDNS   │  │ Traefik  │  │ Authelia │  │ Core Services │ │
│  │ (SSL DNS)  │  │ (multi-  │  │  (SSO)   │  │   (local)     │ │
│  │            │  │ provider)│  │          │  │               │ │
│  └────────────┘  └────┬─────┘  └──────────┘  └──────────────┘ │
│                       │                                          │
│          ┌──────────────┼──────────────┐                        │
│          │  Routes:     │              │                        │
│          │  • Local     │  (labels)    │                        │
│          │  • Remote    │  (YAML files)│                        │
└──────────┼──────────────┼──────────────┼────────────────────────┘
           │              │              │
    Ports  │  HTTP/HTTPS  │              │
    80/443 │              │              │
           ▼              ▼              ▼
    ┌─────────────────────────────────────────┐
    │         REMOTE SERVER (e.g., Pi)        │
    │  ┌──────────┐  ┌──────────┐  ┌───────┐ │
    │  │ Traefik  │  │ Sablier  │  │ Media │ │
    │  │ (local)  │  │ (local)  │  │ Apps  │ │
    │  └──────────┘  └──────────┘  └───────┘ │
    └─────────────────────────────────────────┘

Deployment Process

Step 1: Deploy Core Server

On the core server, run ez-homelab.sh

Use Option 1 to Install Prerequesites
Then Option 2 to Deploy Core Server

This deploys: DuckDNS, Traefik(core), Authelia, Dashboards & Infrastructure

From Dockge you can start/stop any of the stacks or containers.

Port Forwarding:

Forward ports 80 & 443 from your router
Only this server requires port forwarding

Step 2: Deploy Remote Server

On the remote server, run ez-homelab.sh

Use Option 1 to Install Prerequesites
Then Option 3 to Deploy Remote Server

This deploys: Traefik(local), Dashboards & Infrastructure