Operate Starport
Run a Starport gateway or fleet day to day, from authentication and identity to catalog updates, signals, and upgrades.
This area is for operators who keep a Starport gateway or fleet in service. It starts after the first installation and the storage selection.
The topics cover who can open the console and how. They cover how a fleet shares its stores and how the catalog changes over time. They also cover the signals that a monitoring system reads, and how to stop and upgrade a gateway safely.
Each procedure has a verification step that you can run from a shell. Most checks need a gateway key with the admin scope. A local admin token opens the console only from the gateway host or through a launch link.
Starport requires a gateway API key by default. Keep that default on each address that the network can reach.
Starmap state recovery and unrecognized journals
Find the Starmap state that a gateway keeps, and recover safely when the runtime reports an unrecognized journal.
Authentication and the local admin token
Select the authentication mode, understand the exposure tripwire, and use and rotate the local admin token to open the console.