45559c0e-d9d4-4741-94b7-ca25b55059d3
Forgeon Docs

Documentation, guides, and patterns to help you build on Forgeon — from your first deploy to running serious infrastructure.

Deployments

Forgeon deployments: environments, rollouts, runtime state, and operational controls.

Last updated: 2026-03-17

Forgeon deployments are built around environments, a build pipeline, and runtime state. This is the top‑level guide for how deploys work end‑to‑end.

flowchart LR
  A[Intake] --> B[Build]
  B --> C[Artifact]
  C --> D[Runtime start]
  D --> E[Health checks]
  E --> F[Route traffic]

The deployment model

  • Environment — prod / uat / qa / staging / dev / preview
  • Deployment — a build artifact + runtime config for an env
  • Runtime — running container(s) with live traffic state

Typical workflow

  1. Deploy to preview for PRs
  2. Validate in staging
  3. Deploy to prod

What you can control

  • Build system (Template / Nixpacks / Buildpacks)
  • Build and start commands
  • Environment variables per env
  • Rollouts and restarts
  • Domains and SSL

Troubleshooting

App not reachable

  • Ensure your app uses PORT and binds to 0.0.0.0

Runtime shows “Idle” but should be live

  • Check last request, domain configuration, and health checks

Learn next