hetzner-cloud

# Hetzner Cloud Operate Hetzner Cloud through the `hcloud` CLI. When in doubt about server types, prices, locations, images, or flag syntax, run the discovery command rather than rely on this file or pretraining — the CLI is current. ## Authenticate Generate a token in Hetzner Console → project → Security → API Tokens, then either: ```bash hcloud context create <name> # interactive: stored in cli.toml, persists across shells export HCLOUD_TOKEN="…" # CI/scripts: most commands read this automatically ``` `hcloud context create` is the one common case that still prompts even with the env var set — pass `--token-from-env` to skip the prompt in non-interactive sessions. Health check: `hcloud datacenter list`. ## Mental model `hcloud` manages everything inside **Hetzner Cloud**: servers, networks, firewalls, load balancers, volumes, DNS zones, SSH keys, primary/floating IPs, snapshots, certificates, placement groups, storage boxes. It does **not** manage: - **Hetzner Robot** — dedicated/auction servers, separate product and API. - Project creation, billing, team membership, API token issuing — web console only. **Discovery beats memorization.** Pretraining ages; the CLI is current. | Question | Command | |---|---| | Server types and prices | `hcloud server-type list` | | Locations and datacenters | `hcloud location list` | | OS images | `hcloud image list --type system` (add `--architecture arm` for ARM) | | Command/flag details | `hcloud <resource> <verb...