kelin/EZ-Homelab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add multi-server support and update docs

Browse Source 
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.
This commit is contained in:
kelinfoxy
2026-02-05 22:30:52 -05:00
parent 84b2cabacc
commit 5cbb106160
27 changed files with 803 additions and 3300 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/multi-server-implementation-plan.md
View File

@@ -1,5 +1,28 @@
# Multi-Server Traefik and Sablier Implementation Plan
> **⚠️ IMPLEMENTATION STATUS: COMPLETED (with modified approach)**
>
> **Date**: December 2024
> **Status**: The multi-server architecture has been successfully implemented, but with a **simplified approach** that differs from this original plan.
>
> **What Changed:**
> - ❌ **Traefik Multi-Docker Provider**: NOT implemented (complexity, Docker API security concerns)
> - ✅ **Per-Server Traefik**: Each server runs its own Traefik for LOCAL discovery only
> - ✅ **Per-Server Sablier**: Each server runs its own Sablier for LOCAL lazy loading
> - ✅ **Core Routing**: Core Traefik uses file provider (YAML) to route to remote services
> - ✅ **No Docker API TLS**: Servers communicate via HTTP/HTTPS, not Docker API
>
> **Current Documentation:**
> - **Architecture**: See [Ondemand-Remote-Services.md](Ondemand-Remote-Services.md) for the implemented approach
> - **Service Creation**: See [docker-guidelines.md](docker-guidelines.md) for multi-server patterns
> - **How It Works**: See [how-it-works.md](how-it-works.md) for architecture overview
>
> **This Document**: Preserved for historical reference and future consideration. The original plan's centralized Traefik approach may be revisited in the future if label-based remote discovery becomes a priority.
---
# Original Implementation Plan (Historical Reference)
## Executive Summary
This document outlines the implementation plan for enabling label-based automatic routing and lazy loading across multiple servers in the EZ-Homelab infrastructure. The goals are to: