Welcome to Forgeon
What Forgeon is, how the docs are organized, and the fastest path to your first deploy (via GitHub + Dashboard).
Last updated: 2025-10-20
What is Forgeon?
Forgeon is a modern PaaS that takes your code from repo to running: builds, CI, runtime orchestration, domains & SSL, logs, and managed databases. Bring your code; we’ll handle the boring, brittle bits.
Core ideas
- Git in, app out — connect a repo, ship a build, get a live URL with SSL.
- Batteries included — domains, certs, logs, metrics, and managed DBs.
- Predictable ops — sane defaults, clear quotas, and rollbacks when you need them.
How these docs are organized
- Getting Started — shortest path to first deploy:
- Deploy — environments, rollbacks, logs, domains:
- Reference — deeper details:
Prerequisites
- A GitHub repository you can connect (personal or org)
- A web app that binds to 0.0.0.0 and respects the PORT env (Node/Go/Python/Docker all fine)
- A Forgeon account (free tier is fine)
Your first deployment (dashboard only)
quickstart.sh
- Sign in with GitHub on the Forgeon dashboard and approve requested scopes.
- Install the Forgeon GitHub App on your personal account or org (select specific repos or all).
- Create a project → Import from GitHub → pick your repo.
- Review detection (framework, build, output, runtime port) and save.
- Click Deploy → watch build logs → get a preview URL with SSL.
- Add Environment Variables (Settings → Environment) and Redeploy if needed.
- Optional: add a Custom Domain (Domains tab) and point DNS; SSL auto-provisions.
What you’ll learn next
- Deploy flow — build logs, rollbacks, env vars, secrets
→ Deployments - Domains & SSL — automatic certs, custom domains, redirects
→ Domains & SSL - Databases — create a managed Postgres/MySQL/Redis and wire credentials
→ Databases - Runtime configuration — ports, health checks, scaling, timeouts
→ Configuration
Conventions used in these docs
- UI paths are written like:
Projects → New Project → Import from GitHub - Terms: Preview URL (auto domain with SSL), Deployment (build + runtime), Project (your app in Forgeon).
- Callouts highlight tips, warnings, and gotchas. Terminal callouts show “clickable commands” that open pages.
Troubleshooting
- Build succeeded, page blank — ensure your app binds 0.0.0.0 and reads PORT; check Runtime Logs.
- Custom domain pending — verify DNS targets; propagation may take time. Status appears in the Domains tab.
- No commits detected — confirm the GitHub App is installed on the repo (GitHub → Settings → Apps → Installed GitHub Apps → Forgeon).
Add a lightweight /readyz endpoint and configure it as your
health check for faster readiness and clearer failures.