Build with Forge¶
Forge deploys your committed application source with its manifest and runtime configuration. Follow Quickstart to install Aegis, sign in and deploy an existing or new application.
Prepare your application¶
Initialize the repository with Forge to validate an existing manifest or create one for a supported static layout:
Initialization is local and makes no network request. Read Configure your app for the layouts it accepts and for the refusal when it cannot tell which runtime you use.
Build and test the application locally. Running a coding agent through your
Aegis account with aegis gateway enable --agent codex is optional and separate from
Forge; it is not a prerequisite for deployment.
Commit your source and mithran.yaml together, then push the commit you
want deployed to GitHub.
The GitHub origin identifies the default repository, and committed HEAD
identifies the default source. Automation can select a repository, ref or
commit through the supported source flags.
Deploy and keep the result¶
Request deployment from your repository:
The request uses committed source only. Forge may require its GitHub App to be installed and associated with the repository; Connect GitHub explains the four separate facts and the one next action for each state.
On success the command prints aegis: forge deploy accepted <deployment_ref>.
Keep that reference with the commit. Version 0.9.4 has no command that
returns the application's address and no hosted status or rollback command;
see Deployment results and proof for what
the result can and cannot establish.
Access boundaries¶
Your GitHub credentials authorize source-control operations. The Forge GitHub App's grant gives Forge access to one repository for deployment, without adding a deployment workflow to the repository.
Environment, tenant, account, installation and app identity come from authorization and repository context. Review Security and trust before sharing your app.