EZ-Homelab

kelin/EZ-Homelab

Fork 0

Commit Graph

Author	SHA1	Message	Date
Kelin	7c8f128eaf	Update architecture diagram to show public internet routing and HTTP vs HTTPS traffic Changes: - Added public internet layer showing HTTPS traffic flow - Clarified that internal network uses HTTP (no SSL/TLS) - Added traffic flow summary section - Updated 'How It Works' section to explicitly mention HTTPS externally, HTTP internally - Added 'Key Points' section explaining no double encryption The diagram now clearly shows: 1. 🌐 Public Internet → HTTPS (ports 80/443) 2. Core Server (SSL termination) 3. Internal Network → HTTP (no encryption needed) 4. Additional Servers (direct port access)	2026-02-08 15:19:48 -05:00
Kelin	63b2ae8fe0	Update multi-server deployment docs for simplified architecture Changes: - Remove references to local Traefik on additional servers - Update architecture diagram to show direct port exposure - Clarify that additional servers are 'headless' (no local reverse proxy) - Update traffic flow to show direct routing from core to services - Update performance metrics (50MB vs 100MB, 2min vs 5-10min deployment) - Rename 'Remote Server' to 'Additional Server' for consistency The docs now accurately reflect the current simplified architecture where additional servers only run Sablier and expose ports directly.	2026-02-08 15:13:44 -05:00
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

Author

SHA1

Message

Date

Kelin

7c8f128eaf

Update architecture diagram to show public internet routing and HTTP vs HTTPS traffic

Changes:
- Added public internet layer showing HTTPS traffic flow
- Clarified that internal network uses HTTP (no SSL/TLS)
- Added traffic flow summary section
- Updated 'How It Works' section to explicitly mention HTTPS externally, HTTP internally
- Added 'Key Points' section explaining no double encryption

The diagram now clearly shows:
1. 🌐 Public Internet → HTTPS (ports 80/443)
2. Core Server (SSL termination)
3. Internal Network → HTTP (no encryption needed)
4. Additional Servers (direct port access)

2026-02-08 15:19:48 -05:00

Kelin

63b2ae8fe0

Update multi-server deployment docs for simplified architecture

Changes:
- Remove references to local Traefik on additional servers
- Update architecture diagram to show direct port exposure
- Clarify that additional servers are 'headless' (no local reverse proxy)
- Update traffic flow to show direct routing from core to services
- Update performance metrics (50MB vs 100MB, 2min vs 5-10min deployment)
- Rename 'Remote Server' to 'Additional Server' for consistency

The docs now accurately reflect the current simplified architecture where
additional servers only run Sablier and expose ports directly.

2026-02-08 15:13:44 -05:00

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

3 Commits