Profile dashboard

Selecting a saved profile opens its dashboard. The profile address, domain, repository, GitHub token status, Pangolin registration, cloud state, stage progress, and standalone stacks remain visible together.

Read setup progress

The stage table has three operator actions:

Stage	Work it runs
Bootstrap	Create and verify administrative SSH access.
Harden	Apply operating-system, SSH, swap, update, and CrowdSec hardening.
Platform	Run Docker networking, Pangolin proxy, and observability in order.

Use j and k to select a row. Press r to run the selected stage once, including a stage already marked complete. Press v to review the full setup plan.

Dashboard keys

Key	Action
j / k	Select a setup stage.
r	Run the selected stage.
v	Review the full setup plan.
h	Open persisted run history.
s	Open the application stack manager.
e	Edit the normal profile values.
a	Edit advanced connection and credential values.
g	Add, replace, or remove the saved GitHub token.
p	Reveal or hide saved Pangolin access values when available.
c	Check Pangolin registration again.
o	Open DigitalOcean actions when the profile has cloud metadata.
f	Start a fresh local profile while preserving the selected one.
x	Review local profile deletion.
esc	Return to the profile picker.
q	Exit Servestead.

The footer is authoritative when a key is unavailable for the selected profile.

Pangolin access

The dashboard checks the profile’s Pangolin registration and reports incomplete, complete, or unavailable status. Press c to repeat the check. Press p only when you need the initial setup URL or saved administrator credentials. The revealed value appears in the terminal until you hide it or leave the screen.

Cloud actions

Press o on a DigitalOcean-backed profile. Restart and destroy each require a review. Destroy permanently removes the remote Droplet but keeps the local profile, secrets, run history, and destroyed cloud metadata.

Local deletion

Press x to review deletion of the selected local profile. The prompt shows the profile directory and explains that the remote server and cloud resource will not change. Active runs block deletion. To proceed, enter delete <profile-name> exactly as shown.

Export any age identity needed for stack secret recovery before deleting the profile.

Next checks

Use Profiles and run history after a failed or cancelled run. Use GitOps review and sync when the stack manager reports a commit, push, or sync requirement.