Terminology
Common Skyport terms used throughout the panel and daemon documentation.
This page defines the terms used across the Skyport docs.
The panel is the main web application. It handles authentication, administration, node management, locations, users, and server records.
skyportd
Section titled “skyportd”skyportd is the daemon that runs on a node machine. It enrolls with the panel, receives configuration, and manages runtime operations on behalf of the panel.
A node is a machine capable of hosting server workloads. In practice, a node has:
- an FQDN
- a daemon API port
- an SFTP port
- a location assignment
- optional TLS
Location
Section titled “Location”A location is a logical grouping for nodes. Administrators usually use locations for regions such as:
- Frankfurt
- Ashburn
- Los Angeles
- Singapore
Allocation
Section titled “Allocation”An allocation is a bind IP and port combination on a node that can be assigned to a server.
Server
Section titled “Server”A server is the managed workload a user sees in the panel. It belongs to:
- one user
- one node
- one allocation
- one cargo
A cargo is Skyport’s server definition package. It describes how a server should be installed and started, including:
- startup command
- install script
- runtime image choices
- variables
- log handling and stop behavior
If you come from Pterodactyl, think of a cargo as the rough equivalent of an egg.
Configuration token
Section titled “Configuration token”A configuration token is the one-time token generated by the panel for node enrollment. It is used only to bootstrap skyportd.
Daemon secret
Section titled “Daemon secret”The daemon secret is the long-lived credential issued to an enrolled daemon so it can continue talking to the panel securely.
Octane
Section titled “Octane”Laravel Octane is the high-performance application server layer used by the panel.
Swoole
Section titled “Swoole”Swoole is the recommended Octane server backend for Skyport panel deployments.