Utilities
These commands do not belong to a single operational topic and sit 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. Use it when debugging an install or
checking which release a machine is on.
flui versionflui version --latest # show what `env create --latest` would resolve toflui 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, asks for confirmation and reinstalls the CLI
globally.
flui updateThe reinstall runs npm install -g @flui-cloud/cli@<latest>. If you
installed the CLI with pnpm or yarn, the command still works but
leaves a mixed install in your local Node setup. If that matters,
reinstall with your own package manager.
flui reconcile
Reconciles the CLI’s local state with what the API knows. It covers only the DNS configuration, and helps after manual edits to DNS records or to the provider zone, to bring the two views back in line.
flui reconcileflui reconcile --type dnsflui reconcile --dry-run| Flag | Default | Effect |
|---|---|---|
-t, --type <kind> | all | Reconciliation kind. One of dns, all. Repeatable. |
--api-url <url> | from the profile, else http://localhost:3000/api/v1 | Override the API URL for this run. |
--dry-run | none | Show what would be reconciled without applying changes. |
DNS
The dns topic has more commands than this page covers. This page
documents the low-level ones: checking resolvers and cleaning up
leftover records. For everyday DNS work (assigning a zone to a
cluster, publishing the wildcard record that covers every application
on it, and adding a second provider for redundancy), see
Put an application on the internet,
which covers flui dns zone, flui dns wildcard and
flui dns replica end to end, in the CLI and the dashboard.
flui dns resolvers
Shows whether certificates are checked through public resolvers before Flui asks for one. Without public resolvers, a name published a moment ago can look missing for up to an hour.
flui dns resolversflui dns resolvers --cluster production --pin--pin sets public resolvers when they are missing, and the
certificate service restarts once. --json gives output for scripts.
flui dns cleanup
Deletes every A record in the named zone on Hetzner DNS. Use it
after destroying a batch of test clusters that left their hostnames
behind.
flui dns cleanup --domain example.com --dry-run # preview firstflui dns cleanup --domain example.comflui dns cleanup --domain example.com --force # skip confirmation| Flag | Required | Effect |
|---|---|---|
--domain <name> | yes | Zone name on Hetzner DNS. |
-f, --force | no | Skip confirmation. |
--dry-run | no | Preview the records that would be deleted. |
Destructive and irreversible. Always run
--dry-runfirst. The command does not check which records belong to active clusters; it removes everyArecord in the zone.