Profiles and run history
A profile is Servestead’s local record for one server. The startup list shows each saved profile with its address and latest run status. Select one to open its dashboard.
Profile state
Section titled “Profile state”The dashboard combines the profile’s current values with setup and operation state:
- Bootstrap, Harden, and Platform completion.
- Configuration repository path and GitHub token source.
- Pangolin registration and saved access status.
- DigitalOcean resource metadata and destroyed state when present.
- Application stacks found in the configuration repository.
Use e for normal values and a for advanced connection or Pangolin fields. On a saved profile, ctrl+s writes the edit without starting a run.
Run history
Section titled “Run history”Press h from the profile dashboard. Newest runs appear first with status and timestamps. Open a run to inspect:
- Overall status and start or finish time.
- Stage status and the recorded stage error.
- Task event output loaded from the profile’s JSONL log.
- The local log path used for the detail view.
Known profile secrets are replaced before log text is shown. Live output, individual saved lines, and total saved output are bounded; visible markers identify omitted output. Detail loads asynchronously and reads a bounded tail: at most the latest 500 saved events are displayed. The view says when earlier, oversized, or incomplete records were omitted, while retaining valid events around them.
Use the scrolling keys shown in the footer, then press esc to return to the run list or dashboard.
Local file layout
Section titled “Local file layout”Servestead uses the operating system’s user configuration directory unless SERVESTEAD_CONFIG_DIR sets another root. Each profile stores:
| File | Contents |
|---|---|
profile.json |
Address, users, domain, repository, and cloud metadata. |
state.json |
Active run, setup stages, stack commit, and run summaries. |
secrets.json |
Generated platform credentials, GitHub token, and stack age identity. |
logs/<run-id>.jsonl |
Structured task events for one run. |
Profile directories and sensitive files use owner-only permissions.
Delete a local profile
Section titled “Delete a local profile”Press x on the dashboard and read the displayed path and effect. Deletion removes local metadata, secrets, state, and logs. It does not change the remote server, cloud resource, or configuration repository. Servestead refuses the deletion while a run is active.
Enter delete <profile-name> exactly as shown to proceed. Back up the profile’s age identity first when any encrypted stack values still matter.
Expected result
Section titled “Expected result”You can identify the latest run outcome, open the exact failed stage and log, and distinguish local profile state from the server, provider, and Git repository before taking corrective action.