Best practices

One page per task, for the jobs that take more than one call: the requests in order, the in-guest work between them, and what goes wrong in the middle.

Facts — limits, field names, error codes — belong to the guide that owns the resource, and a page here links rather than repeats.

Every page exists twice, the markdown and an .html twin. Fetch the markdown and read it whole rather than through a summarizing fetch: a summary drops the step you were missing.

• Recreate a VM — grow a root disk, replace a machine, move off failed hardware
• Debug a VM that will not come up — what to read when there is no console
• Harden a VM — firewall and sshd changes that cannot lock you out
• Put a CDN in front — serve cacheable traffic near the reader, and take those bytes off the egress meter
• Self-host storage — S3 or a shared filesystem on a VM you own
• Build a private mesh — private addressing between your own VMs
• Watch your credits — what to poll, what to cut, and what happens at zero