Your apps

Each app has a Settings tab (General, App, Prompts, Labels, Webhooks, Machines, Danger zone). The things most people reach for are below.

How an app runs

The repository says how to run itself in forge.json at its root. Only app.run is needed; health is the page the forge polls until the app answers.

Domains

Every app has an address on the forge. To use your own, open the app's Settings, App pane, add the domain, and put the DNS records it shows at your registrar. The forge checks them and says what is missing. Reference: an app's own domain.

Environment and secrets

Variables are set in the app's Settings, App pane: a name, a value, and where it applies (production or previews). A name ending _KEY, _SECRET or _TOKEN is hidden after you save it. A .env.example file in the repository opens as a table of what the app needs. Never commit a real secret.

Your own account's keys, tokens and passkeys are at /settings/secrets, /settings/tokens and /settings/passkeys.

Schedules

An app can run a path on a timer. Declare it in forge.json, beside run:

{
  "app": { "run": "bun run src/server.ts" },
  "schedules": [
    { "name": "print", "cron": "30 6 * * *", "timezone": "America/Chicago", "path": "/jobs/print" }
  ]
}

The forge wakes a sleeping app at that time and calls the path. Printing a daily report is just a schedule that calls a page which produces it.

Backups of an app's data

An app's own data lives under FORGE_APP_DATA. See an app's encrypted backup.

Which files open

Every kind of file the viewer draws, and its size limit: which files open.

Reference: apps. Next: Hosting forges.

Every feature note, by topic: the reference notes.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs