Deploy¶
Forge deploys committed source from your GitHub repository. Run the command
from the repository that contains mithran.yaml:
Before deployment¶
Review the manifest and source, run the app's local checks, then commit and
push the changes you want deployed. The request selects committed HEAD; it
does not upload local objects and does not include uncommitted files.
You must be signed in with aegis auth login. Without a bound account the
command exits 66 and reports that you must complete sign-in for this
profile first.
Forge may need its GitHub App installed and associated with the repository before it will accept the request; 0.9.4 does not print a setup URL or open a consent page. Your own GitHub credentials still perform ordinary Git operations, and Forge adds no workflow to the repository. Connect GitHub explains the four checks and what each state needs.
What the command returns¶
On success the human-readable output is
aegis: forge deploy accepted <deployment_ref>. Keep the reference with the
commit you pushed: it is the record of the request.
aegis forge deploy --json prints a redacted evidence envelope on stdout;
Deployment results and proof lists its
keys. Typed structured source and deployment refusals also use a value-free
stdout envelope and a nonzero exit. Configuration, account and Auth failures
instead use stderr with empty stdout, even with --json. The human form
prints refusals to stderr.
Version 0.9.4 has no command that returns the deployed application's address,
no hosted status command and no rollback command. Do not construct an address
from the repository or app name and do not expect forge status to work.
See Deployment results and proof for the
evidence you can keep.
Select source for automation¶
The default request uses the GitHub origin and committed HEAD. Automation
can override the selection:
--sha selects a commit instead of --ref, and the two cannot be combined.
The selection must name committed source reachable from the repository; an
unresolvable selection is refused as forge_source_unavailable with exit
64 before any request is made.
Environment, tenant, account, installation and app identity come from authorization and repository context. Deployment flags cannot override them.
Update an application¶
Commit and push each change, then deploy again. Each deployment describes one commit, so keep each returned reference with its commit. A ready deployment does not by itself prove availability, recovery or scale.