fuoco

Crates.iofuoco
lib.rsfuoco
version0.0.5
created_at2025-06-16 16:06:20.424068+00
updated_at2025-07-03 13:08:17.717304+00
descriptionA CLI tool for provisioning ephemeral VMs on AWS, GCP, and Hetzner through a unified interface.
homepage
repositoryhttps://github.com/x71c9/fuoco
max_upload_size
id1714456
size37,274
x71c9 (x71c9)

documentation

README

fuoco

Ephemeral VM provisioner for AWS, GCP, and Hetzner.

fuoco automates a built-in Terraform template to provision a single VM in AWS, GCP, or Hetzner, executes a startup script via cloud-init/user-data, and destroys all resources on termination.

Features

  • Single-VM workflow – Apply and destroy with a single command.
  • Multi-cloud support – AWS | GCP | Hetzner through a unified CLI.
  • Built-in Terraform templates – No separate Terraform code to maintain.
  • Startup script support – Inject Bash scripts at boot via cloud-init.
  • Debug mode – --debug streams Terraform logs for troubleshooting.
  • Automatic cleanup – Ensures a fresh workspace on every run.

Requirements

  • Rust toolchain to build fuoco.
  • Terraform (>= 0.12) available in system PATH.
  • Cloud credentials:

    • AWS: via ~/.aws/credentials or environment variables.

    • GCP: via gcloud auth application-default login or GOOGLE_CLOUD_PROJECT env var.

    • Hetzner: via HCLOUD_TOKEN env var.

Usage

fuoco deploy --provider <aws|gcp|hetzner> [OPTIONS]

If somethig goes wrong it is possible to undeploy with:

fuoco undeploy --provider <aws|gcp|hetzner> [OPTIONS]
Option Description
--provider <aws|gcp|hetzner> Cloud to deploy (aws, gcp, or hetzner).
--region <REGION> AWS region, GCP zone, or Hetzner location (e.g. us-east-1, us-central1-a, nbg1).
--instance-type <TYPE> VM size (defaults: t4g.nano AWS, e2-micro GCP, cx11 Hetzner).
--script-path <FILE> Path to a Bash script to execute on VM startup.
--debug Print Terraform init/apply/destroy logs (for debugging).
-h, --help Show this help message.

Press Ctrl+C or send SIGTERM to destroy the VM and exit.

Examples

fuoco deploy --provider aws --script ./startup.sh

Built‑in Terraform Templates

Templates embedded under templates/<provider>/main.tf:

How It Works

  1. Prepare a hashed temp workspace and copy the Terraform files.
  2. terraform init the provider.
  3. terraform apply with auto-approve and injected vars (region, instance-type, script, etc.).
  4. Wait for Ctrl+C/SIGTERM (or panic) to trigger terraform destroy.
  5. On each run, remove stale workspace so you always use the latest templates.

Debugging & Troubleshooting

  • Use --debug to view full Terraform logs.
  • For console‑level logs, add tee /dev/console to the cloud‑init user‑data sequence.

Contributing

Contributions are welcome. Open issues or PRs for bugs, features, or improvements.

Commit count: 12

cargo fmt