fugueDOCS
Docs

Deploy from your terminal

Install the fugue CLI, create your first API key, and ship a service from your terminal in a few minutes.

01Install the CLI

The fugue CLI is a semantic wrapper over the Fugue control-plane API. Install it with a single command.

macOS / Linux
curl -fsSL https://raw.githubusercontent.com/yym68686/fugue/main/scripts/install_fugue_cli.sh | sh
Windows PowerShell
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/yym68686/fugue/main/scripts/install_fugue_cli.ps1 | iex"

Confirm it is on your PATH:

fugue version

02Get your first API key

You authenticate the CLI with an API key minted from the console. For security the secret is shown only once, so copy it right away.

  1. Sign in to the console.
  2. Open the Access keys page from the sidebar.
  3. Click New key, give it a name, pick the scopes it needs, and create it.
  4. Copy the secret from the dialog — it will not be shown again.
Go to Access keys
Self-hosting Fugue? The Access keys page lives at your own console URL followed by /keys.

03What the API key is for

The API key authenticates the CLI — and any direct API calls — to your tenant on the control plane. Every command you run, from deploy to logs to scaling, is authorized by the key you provide. Nothing runs against your workspace without one.

  • Tenant API key — for everyday work: deploy apps, read logs, and manage services inside your workspace. Each key is limited to the scopes you grant it.
  • Workspace admin key — your workspace's built-in high-privilege key. It is what mints and manages the other keys, so it is never shown for deletion.
  • Platform / bootstrap key — reserved for cluster-wide admin commands. Keep it secret and use it only when an operation truly requires it.
Keys are sealed and encrypted at rest. You can disable or delete any key from the Access keys page at any time.

04Authenticate and deploy

Save the key once, then deploy straight from a project directory. The CLI resolves your tenant, project, and app by name.

# save the key once (stored in your fugue config)
fugue auth login --token <your-api-key>

# …or export it for the current shell only
export FUGUE_API_KEY=<your-api-key>

# build and deploy the current directory
fugue deploy .

# list apps and stream logs
fugue app ls
fugue app logs <app-name>
On Fugue Cloud the base URL is detected automatically. For a self-hosted control plane, set FUGUE_API_URL (or FUGUE_BASE_URL) to your API endpoint before running commands.

05Connect your own server

Want Fugue to schedule workloads onto your own VPS? Open Servers, click Connect node, name the machine, and run the generated one-line command on it as root. The node joins the cluster in about a minute and then appears in your node list.

Go to Servers

06Handy commands

fugue deploy .Build and deploy the current directory
fugue app lsList your applications
fugue app logs <name>Stream logs for an app
fugue find <name>Resolve and inspect a resource by name
fugue version --check-latestCheck whether a newer CLI is available
fugue upgradeUpgrade the CLI in place
fugue --helpShow the full command reference

Ready to deploy?

From blank to a live service in minutes.

Create account