F Forge DocsRepository ↗FeaturesUser manual

Management / user manual

Apps

Manages container applications, Git sources, and Compose stacks. Creates deployments and revisions that Beacon builds or runs.

Purpose

Create the workloads and identities your organization manages.

ARCHITECTURE

Workload management flow

Forge workload lifecycle

01Administratorconfigure
02Forge Webpersist
03Workload recordcoordinate
04Operationexecute
05Beacon
templateresourcesallocationnode health

How to use it

Operator workflow

  1. 01

    Open Apps from the administrator panel and review the current state.

  2. 02

    Set the specific configuration that expresses the desired apps outcome.

  3. 03

    Save deliberately, then follow the operation, activity, health, or runtime observation that confirms the result.

  4. 04

    Keep the before-and-after evidence in Activity and verify the workload path before relying on the change.

What Forge owns

Boundary and safety

The panel records workload intent. Beacon performs the Docker and filesystem action against the selected node.

Use deliberate changes

Review the affected node, workload, route, or secret before saving. Capture state and health evidence before changes that affect data or public traffic.

Before you finish

Verification checklist

  • The operator has the required administrative role.
  • The intended node, workload, or project is selected.
  • The resulting operation or observation reaches a terminal state.
  • A rollback path exists before changing production traffic or storage.

Continue the manual

Use this feature in the wider Forge workflow.

Move from platform understanding to the relevant operating guide when you need exact environment, network, deployment, or recovery steps.