GSP/Panel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

worshop work

Browse source
This commit is contained in:
Frank Harris 2026-06-08 16:09:54 -05:00
parent 0d44c65ea5
commit 3829a4a83d
92 changed files with 487 additions and 110 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/architecture/AI_GSP_ARCHITECTURE.md
View file

@ -1,5 +1,7 @@
# GSP Component Architecture
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
This repository contains the related GSP components together:
- `/Agent-Windows` - Cygwin/Windows game server agent.

9
docs/architecture/API_REFERENCE.md
View file

@ -1,5 +1,7 @@
# API Reference
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Scope
This is the master reference for:
@ -193,9 +195,10 @@ Current preferred Workshop/content flow:
1. Panel validates Workshop IDs
2. Panel writes manifest JSON to server home
3. Panel stages bundled helper script to agent host via `writefile`
4. Panel runs helper with `exec`
5. Agent logs/install output is returned to Panel
3. Panel writes a generated per-job shell script to server home via `writefile`
4. The job script writes a temporary SteamCMD runscript
5. Panel runs the generated job script with `exec`
6. Agent logs/install output is returned to Panel
Common manifest fields:

2
docs/architecture/LIBRARY_REFERENCE.md
View file

@ -1,5 +1,7 @@
# Library Reference
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Scope
This file documents the shared Panel libraries and helper entrypoints that multiple modules reuse.

2
docs/architecture/MODULE_DEPENDENCIES.md
View file

@ -1,5 +1,7 @@
# Module Dependencies
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Scope
This file maps how Panel modules depend on:

7
docs/architecture/PANEL_AGENT_COMMANDS.md
View file

@ -1,5 +1,7 @@
# Panel-Agent Commands
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Scope
This file is the command catalog for the XML-RPC surface between the Panel and the agents.
@ -101,8 +103,9 @@ Common patterns:
Current preferred implementation path:
- `addonsmanager` stages a manifest and helper script through `writefile`
- it executes the helper through `exec`
- `addonsmanager` stages a manifest and generated per-job script through `writefile`
- the generated script creates a temporary SteamCMD runscript and runs `steamcmd +runscript`
- it executes the generated job script through `exec`
- it records per-server items and policies in Panel database tables
- it uses `steam_workshop` only as legacy compatibility, not as the primary workflow
- no new Workshop-specific business logic should be added to agents for the current design

3
docs/architecture/PANEL_AGENT_FLOW.md
View file

@ -1,5 +1,7 @@
# Panel Agent Flow
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Overview
The Panel does not directly run servers. It prepares the request, sends it to the agent, and interprets the response.
@ -100,4 +102,3 @@ Recommended status fields:
- The agent should be the source of truth.
- Marker files may exist, but they should be treated as hints only.
- The same high-level flow should work for Linux and Windows/Cygwin.

2
docs/architecture/REPOSITORY_OVERVIEW.md
View file

@ -1,5 +1,7 @@
# Repository Overview
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Purpose
This repository contains the GSP game server hosting platform:

2
docs/architecture/RPC_STATUS_REPAIR_REPORT.md
View file

@ -1,5 +1,7 @@
# RPC Status Repair Report
Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)
## Purpose
This report documents the investigation and repair for the Panel message: