F Forge DocsRepository ↗FeaturesUser manual

Infrastructure / user manual

Files and Terminal

Administers host files and shells. Uses privileged node-side access; grant only to trusted operators.

Purpose

Describe placement, networking, storage, and the nodes that execute workloads.

ARCHITECTURE

Node placement and runtime flow

Private node network

01Administratordesired state
02Forge APIreserve
03Placement recordauthenticated command
04Beacon nodecontainer/files
05Docker runtime
node healthcapacityallocation or path availability

How to use it

Operator workflow

  1. 01

    Open Files and Terminal from the administrator panel and review the current state.

  2. 02

    Set the specific configuration that expresses the desired files and terminal 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

Infrastructure changes affect execution boundaries: nodes, allocations, mounts, database hosts, and privileged host access. Keep Beacon and private services off the public internet.

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.