Deploy¶
Forge deploys committed source from your GitHub repository. Run the
command from the repository containing your application's
mithran.yaml:
Before deployment¶
Review the manifest and source, then run your app's local checks. Commit
and push the desired changes to the GitHub origin before deploying. The
deployment request selects committed HEAD; it does not upload local
Git objects or include uncommitted files.
Complete Forge GitHub App authorization in your browser when deployment requires repository access. Git operations use your own GitHub credentials, while Forge's authorization lets it read the repository. Forge adds no deployment workflow to your repository.
Find your URL¶
The deploy command returns a deployment reference. If deployment has
succeeded and the route is ready, human-readable output also includes an
application_url line with the application's HTTPS address.
Keep the deployment reference and inspect it when the URL is not yet
available. Replace DEPLOYMENT_REF with the returned value:
Status displays application_url when deployment status is Succeeded
and route status is Ready. Open the returned address in your browser
to inspect the application.
Pending, failed, or no-longer-serving deployments have no current URL. An older server can also omit the field. If a successful, ready deployment has no URL, retain its reference and contact Support. Do not infer an address from the app or repository name.
Add --json to deploy or status commands for structured output. When
available, the response contains the top-level application_url field;
automation must allow it to be absent or null.
Select source for automation¶
The default request uses the GitHub origin and committed HEAD.
Automation can select source with --repo, --ref, or --sha;
--ref and --sha cannot be used together.
Environment, tenant, account, installation, and app identity come from authorization and repository context. Deployment flags cannot override these values.
Update or restore an application¶
Commit and push each update before deploying it. Keep the new deployment reference with the selected commit so you can inspect the result or request restoration of its previous route pointer.
Read CLI reference for status, versions, and rollback commands. A ready route does not prove your application's availability, recovery, or scale requirements.