[Feature]: Single machine-readable data file for server metadata and default ports
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start by reading lgsm/modules/info_messages.sh, the per-server lgsm/config-default/config-lgsm/<server>/_default.cfg files, and lgsm/data/serverlist.csv to see how port metadata is currently represented. The issue proposes a new lgsm/data/servers.json and CI validation, but leaves the schema, coverage of every server, and handling of ports without known defaults to be worked out. Done means the metadata is complete and dependable enough for scripts, CI, and the website to use.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Add one machine-readable data file that holds the definitive per-server metadata, starting with port definitions, so the scripts, the docs and the website all read the same source instead of each working it out separately.
Problem
Default ports are currently spread across several places:
- the port tables printed by
detailslive inlgsm/modules/info_messages.sh(labels, protocols and variable names) - the default values live in
lgsm/config-default/config-lgsm/<server>/_default.cfg, but only for some servers and only some ports - other defaults are only implied by
lgsm/modules/info_game.shfallbacks or by the game's own default config in Game-Server-Configs - some games have no default anywhere in LinuxGSM and the value only exists in the game's own documentation
Anything outside the main script that needs ports has to scrape shell code. The new linuxgsm.com site needs a port table for every server, and building it from the current files gave only about half of the default values directly from this repo. The rest had to be guessed or taken from another source, which is not reliable enough to publish.
Proposal
Add a data file (for example lgsm/data/servers.json, next to serverlist.csv) with one entry per server. For ports:
{
"csgoserver": {
"ports": [
{ "setting": "port", "label": "Game", "default": 27015, "protocol": "udp" },
{ "setting": "port", "label": "Game", "default": 27015, "protocol": "tcp" },
{ "setting": "sourcetvport", "label": "SourceTV", "default": 27020, "protocol": "udp" }
]
}
}
Then:
- Generate or validate the
fn_portlines ininfo_messages.shand the port values in_default.cfgfrom that file, or have CI fail if they disagree, so there is only one place to edit. - Add a check in CI that every server in
serverlist.csvhas an entry, and every port thedetailscommand prints has a default value. - Publish the file so linuxgsm.com, the docs and other tools can read it directly.
Other uses
The same file could hold other facts that are currently scattered or only in the docs, for example engine, whether SteamCMD is used, whether a Steam login or a game server token is needed, default install size, supported distros, and the config file paths. The linuxgsm.com server pages already show several of these.
Notes
- Servers where LinuxGSM currently has no default for a port would need the value confirmed from the game's own documentation before it goes in.
- A follow-up could let
detailsread from the same file, but that is not required for the first version.
- Lingua principale
- Shell
- Stelle
- 4.9k
- Fork
- 866
- Merge medio
- 17h 58m
- PR unite (30g)
- 100
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
GameServerManagers/LinuxGSM#5242 ·
I maintainer di solito rispondono entro 1 giorno
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
GameServerManagers/LinuxGSM#5241 ·
I maintainer di solito rispondono entro 1 giorno
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
GameServerManagers/LinuxGSM#5240 ·
I maintainer di solito rispondono entro 1 giorno
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
GameServerManagers/LinuxGSM#5238 ·
I maintainer di solito rispondono entro 1 giorno
-
engine: null game: Teamspeak 3
Difficoltà 3/5 Mezza giornata Idoneità per principianti 66/100
GameServerManagers/LinuxGSM#5237 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di GameServerManagers/LinuxGSM
Issue simili
-
enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
varnish/helm-varnish#173 ·
I maintainer di solito rispondono entro 2 giorni
-
bump version [nginx2root]Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Update: sanitize-htmlAperta📦 Update Request
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
cdnjs/packages#2225 · 1 commento ·
I maintainer di solito rispondono entro 3 giorni
-
good first issue help wanted testing
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100