[Feature]: Single machine-readable data file for server metadata and default ports
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 35/100
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- Shell
- Étoiles
- 4.9k
- Forks
- 866
- Merge moyen
- 17 h 58 min
- PR mergées (30 j)
- 100
Préparer son environnement
Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulté 2/5 1-3 heures Accessibilité débutants 84/100
GameServerManagers/LinuxGSM#5242 ·
Les mainteneurs répondent en général sous 1 jour
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
GameServerManagers/LinuxGSM#5241 ·
Les mainteneurs répondent en général sous 1 jour
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
GameServerManagers/LinuxGSM#5240 ·
Les mainteneurs répondent en général sous 1 jour
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
GameServerManagers/LinuxGSM#5238 ·
Les mainteneurs répondent en général sous 1 jour
-
engine: null game: Teamspeak 3
Difficulté 3/5 Une demi-journée Accessibilité débutants 66/100
GameServerManagers/LinuxGSM#5237 ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de GameServerManagers/LinuxGSM
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 80/100
nolte/claude-goose#18 ·
-
gated_tree trusts assume-unchanged entries, and can leave its temporary directory on a signalOuvertedecision
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
btclib-org/claude-process#609 · 1 commentaire ·
-
enhancement good first issue
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 84/100
varnish/helm-varnish#173 ·
Les mainteneurs répondent en général sous 2 jours
-
bump version [nginx2root]Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100