Reference
Architecture
SkyPort architecture, runtime boundaries, and code layout.
SkyPort is split into a backend Go server, a standalone Go CLI, a React dashboard, and a Nuxt-based docs site.
Repository Layout
SkyPort/
├── backend/ # Go API server, modules, and embedded UI host
├── cli/ # Standalone Go CLI and TUI
├── docs/ # Nuxt 3 + Docus documentation site
├── frontend/ # Product dashboard
├── installer/
└── scripts/
Backend Responsibilities
- API routing and middleware
- Docker operations
- PM2 operations
- VPS records and SSH sessions
- Metrics and health
- Reverse proxy generation
- Marketplace catalog and install records
CLI Responsibilities
- local config and profiles
- login/logout/whoami
- server profile management
- Docker and PM2 operator commands
- project and deployment workflows
- SSH terminal access
- web UI and TUI launchers
Runtime Flow
CLI or dashboard request
-> authenticated API call
-> module handler
-> backend service or host command
-> JSON or live stream response
Data And Config
~/.skyport/
├── config.yaml
├── data/
├── workspace/
├── logs/
├── cache/
└── tmp/
Accuracy Rule
If a feature is not visible in the repository modules, it should not appear here as production behavior.
Next
- Read CLI Reference.
- Read Configuration.
- Read API Reference.
