uncloud

Topics in the source

• Uncloud Cluster Management
• When to Activate
• How It Works
• Examples
• Core Concepts
• CLI Quick Reference
• Machines
• Services

Reference for the uc CLI — a decentralised self-hosting platform using Docker containers, WireGuard mesh networking, and Caddy reverse proxy. Use this skill when working with Uncloud clusters, especially when: Bootstrapping or joining machines with uc machine Deploying services from Compose files with uc deploy Publishing HTTP, HTTPS, TCP, or UDP ports through Uncloud Configuring Caddy ingress with x-caddy, x-ports, or --caddyfile Routing external LAN devices through the cluster proxy Inspecting logs, service state, volumes, DNS, or machine placement Uncloud runs Docker services across peer machines connected by a WireGuard mesh. Each machine is an equal cluster member; services communicate on the overlay network and Caddy runs globally to terminate public HTTP/HTTPS traffic. Compose files can use Uncloud extensions for ingress, placement, and generated Caddy configuration, while the uc CLI handles image distribution, scheduling, scaling, logs, and cluster state. No central control plane — all machines are equal peers connected by WireGuard Caddy runs as a global service on every machine; auto-obtains TLS from Let's Encrypt Overlay network — services communicate via 10.210.0.0/16 b

This is an excerpt. Refer to the complete source and its current requirements.