[Feature]: Single machine-readable data file for server metadata and default ports
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Shell
- Estrellas
- 4.9k
- Forks
- 866
- Merge medio
- 17 h 58 min
- PR fusionados (30 d)
- 100
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
GameServerManagers/LinuxGSM#5242 ·
Los mantenedores suelen responder en 1 día
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
GameServerManagers/LinuxGSM#5241 ·
Los mantenedores suelen responder en 1 día
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
GameServerManagers/LinuxGSM#5240 ·
Los mantenedores suelen responder en 1 día
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
GameServerManagers/LinuxGSM#5238 ·
Los mantenedores suelen responder en 1 día
-
engine: null game: Teamspeak 3
Dificultad 3/5 Medio día Aptitud para principiantes 66/100
GameServerManagers/LinuxGSM#5237 ·
Los mantenedores suelen responder en 1 día
Todos los issues de GameServerManagers/LinuxGSM
Issues similares
-
enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
varnish/helm-varnish#173 ·
Los mantenedores suelen responder en 2 días
-
bump version [nginx2root]Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Update: sanitize-htmlAbierto📦 Update Request
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
cdnjs/packages#2225 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
good first issue help wanted testing
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100