uncloud
Use when managing an Uncloud cluster — deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes with the `uc` CLI.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- affaan-m/ECC @ d3b8a3e90890
- Path
- skills/uncloud/SKILL.md
- License
- MIT
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Uncloud Cluster Management Reference for the `uc` CLI — a decentralised self-hosting platform using Docker containers, WireGuard mesh networking, and Caddy reverse proxy. ## When to Activate 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 ## How It Works 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. ## Examples ```bash uc machine init user@host --name machine-1 …