Utilities

A handful of commands that do not belong to a single operational topic and live at the top level of the CLI.

flui version

Prints the CLI version and the platform release it pins — the component image tags and the bootstrap revision a fresh flui env create would install. Handy when debugging an install or confirming which release a machine is on. See Creating a cluster for what release pinning means.

flui version
flui version --latest   # show what `env create --latest` would resolve to
flui version --json

Flag	Effect
--latest	Show the rolling development tags (bootstrap master, :latest images) that flui env create --latest resolves to, instead of the pinned release.
--json	Machine-readable output.

flui update

Checks npm for a newer published version of @flui-cloud/cli and, if there is one, reinstalls the CLI globally after asking for confirmation.

flui update

The reinstall uses npm install -g @flui-cloud/cli@<latest> under the hood. If you originally installed the CLI with pnpm or yarn the command still works, but it produces a mixed install on the local Node setup; reinstall manually with your package manager of choice if that matters.

flui reconcile

Reconciles the CLI’s local state with what the API knows. Today it covers the DNS configuration only — useful after manual edits to DNS records or to the provider zone, to line the two views back up.

flui reconcile
flui reconcile --type dns
flui reconcile --dry-run

Flag	Default	Effect
-t, --type <kind>	all	Reconciliation kind. Available today: dns, all. Repeatable.
--api-url <url>	from profile	Override the API URL for this run.
--dry-run	—	Show what would be reconciled without applying changes.

flui dns cleanup

Deletes every A record in the named DNS zone on the provider. Typically used after destroying a batch of test clusters that left their hostnames behind.

flui dns cleanup --domain example.com --dry-run    # preview first
flui dns cleanup --domain example.com
flui dns cleanup --domain example.com --force      # skip confirmation

Flag	Required	Effect
--domain <name>	yes	Zone name on the provider.
-f, --force	no	Skip confirmation.
--dry-run	no	Preview the records that would be deleted.

⚠️ Destructive and irreversible. Always run --dry-run first; the command does not look at which records belong to active clusters, it removes every A record in the zone.