Skip to content
Docs

inquir deploy

Package and deploy a serverless function from source or an SDK asset.

@inquir/compute-cliv0.3.0 · Node.js 22+

Usage#

inquir deploybash
inquir deploy [path] [options]

Options#

OptionDescription
--name <name>Function name; defaults to the package or directory name.
--runtime <rt>Override detection: nodejs22, python312 or go122.
--handler <spec>Force handler mode with module.export.
--start <command>Force web mode; the platform supplies PORT.
--mode <handler|web>Override the detected execution mode.
--asset <name>Deploy a defineFunction asset from an SDK workspace.
--stage <name>Deployment stage; alias: --environment.
--set KEY=VALUESet a function environment variable; repeatable.
--env-file <path>Load function environment variables from a dotenv file.
--memory <mb>Function memory limit in MB.
--timeout <ms>Function execution timeout in milliseconds.
--layer <id>Attach a layer by ID; repeatable.
--workspace <id|slug>Target this workspace within your credential permissions.
--env <name>Use a named CLI credential environment.
--no-logsWait for completion without streaming build logs.
--ciUse plain CI output and a non-zero exit code on failure.
--dry-runInspect the detection plan and package without deploying.
--jsonPrint machine-readable results.

Global flags, environments and CLI credentials

Examples#

Example 1bash
inquir deploy ./api
Example 2bash
inquir deploy --asset hello
Example 3bash
inquir deploy --dry-run

Behavior#

A positional path is a source directory. Use --asset for an SDK asset name. For long-lived containers use apps deploy.

--env selects CLI credentials; --stage selects a deployment stage.

Guides#