forge app deploy

Deploy an app via git SHA or artifact upload.

Command

forge app deploy <app-id> [--sha <git-sha>] [--file <path>] [--env <name=value>]

Name	Type	Required	Notes
`app-id`	string	yes	App ID ( `app_*` )

Flag	Type	Default	Notes
`--sha`	string	—	Git SHA for git-triggered deploy
`--file`	path	—	Path to artifact tarball for upload deploy
`--env`	string[]	—	Environment variables (repeatable: `--env KEY=val` )

Either
--sha
or
--file
must be provided, but not both.

Git-triggered deploy:

forge app deploy app_xxxxx --sha a1b2c3d

Artifact upload:

forge app deploy app_xxxxx --file ./dist/app.tar.gz --env NODE_ENV=production

Exit code	Meaning
0	Deploy triggered successfully
1	Invalid input or missing --sha/--file
2	Auth failure
3	App not found
4	Build failed

Either --sha or --file — you must provide one. Providing both or neither is an error.
Async build — the command returns as soon as the build is queued. Use
```
forge app deploy-status <id>
```
to track progress.
Large artifacts — file uploads over 100 MB may timeout. Use git-triggered deploys for large apps.

{auto-injected}