lift stack

Install multi-tool stacks from the OneLift registry with sequential tool installation, variable overrides, and domain configuration.

lift stack

Install multi-tool stacks from the OneLift registry. A stack is a curated bundle of tools that are installed sequentially in the correct order with pre-configured connections between them.

Subcommands

lift stack install

Install a stack on the server. Tools are installed one by one in the order defined by the stack. Each tool's variables are resolved independently, and tools can reference previously installed tools via linked variables.

FlagDescriptionDefault
--var KEY=VALUEOverride a variable for all tools. Can be repeated-
--domain <domain>Domain name passed to all tools (sets APP_DOMAIN)-
--skip-optionalSkip optional tools in the stackfalse
--continue-on-errorContinue installing remaining tools if one failsfalse
# Install the monitoring stack
lift stack install monitoring

# Install with a domain for Traefik routing
lift stack install webdev --domain app.example.com

# Skip optional tools
lift stack install monitoring --skip-optional

# Continue even if a tool fails
lift stack install monitoring --continue-on-error

How It Works

  1. The stack definition is fetched from the registry, including all tool manifests
  2. Each tool manifest is converted from registry format to CLI format
  3. Tools are installed sequentially in the defined order
  4. After each tool installs, its state is saved and made available to subsequent tools via linked variables
  5. Stack-level after_<toolname> hooks run after each tool (e.g., configuring Grafana datasources after Grafana installs)

Some stacks require a paid license. The requiredTier field on a stack determines the minimum plan needed:

TierAccess
freeNo license required
proRequires Pro license
enterpriseRequires Enterprise license

If you attempt to install a paid stack without a valid license, you'll be prompted to set one with lift license set <key>.

Available Stacks

Use lift catalog to see all available stacks, or lift catalog info <stack> for details:

# List all stacks
lift catalog

# See stack details and tool list
lift catalog info monitoring