CLI

The iii CLI: discover commands, trigger functions, and manage iii itself.

For the most current list of commands, flags, and defaults, ask the binary directly:

iii --help            #lists iii's flags and available subcommands
iii subcommand --help #lists the specific actions each sucommand accepts

Each subcommand’s help also provides the defaults and environment variables that affect each command.

The full CLI surface, including iii worker and iii console, is also published as an automatically generated CLI reference.

Subcommands

Subcommand	What it does
iii trigger	Invoke a registered function on a running engine. See Triggering functions.
iii worker	Manage workers: add, remove, list, start/stop, update, verify. See Workers.
iii project	Manage iii projects: scaffold a new one, generate Docker assets. See Deployment.
iii console	Launch the iii web console. See Console.
iii cloud	Manage hosted iii deployments. See Managing iii Cloud deployments.
iii update	Update iii and its managed binaries. See Updating iii itself.

Running iii with no subcommand starts the engine from ./config.yaml (or the path passed to --config). When the file doesn’t exist yet, iii offers to create it with an empty workers list (and creates it without asking in non-interactive sessions); add workers with iii worker add.

Managing iii Cloud deployments

The iii cloud subcommand group will manage hosted iii deployments. See Deployment for details about the iii cloud.

iii’s cloud will be available soon.

Updating iii

iii update refreshes iii and its managed binaries to their latest versions. This is distinct from iii worker update, which refreshes pinned worker versions inside a project.

Specific targets can be updated individually via iii update [target]. Run iii update --list-targets to see the list of targets.