feat(newserver): Core Keeper

[h3o66]

Description

Add Server Core Keeper

Fixes #3855

Type of change

• [ ] Bug fix (a change which fixes an issue).
• [ ] New feature (change which adds functionality).
• [x] New Server (new server added).
• [ ] Refactor (restructures existing code).
• [ ] Comment update (typo, spelling, explanation, examples, etc).

Checklist

PR will not be merged until all steps are complete.

• [x] This pull request links to an issue.
• [x] This pull request uses the develop branch as its base.
• [x] This pull request Subject follows the Conventional Commits standard.
• [x] This code follows the style guidelines of this project.
• [x] I have performed a self-review of my code.
• [x] I have checked that this code is commented where required.
• [x] I have provided a detailed with enough description of this PR.
• [x] I have checked If documentation needs updating.

Documentation

If documentation does need updating either update it by creating a PR (preferred) or request a documentation update.

• User docs: https://github.com/GameServerManagers/LinuxGSM-Docs
• Dev docs: https://github.com/GameServerManagers/LinuxGSM-Dev-Docs

Thank you for your Pull Request!

[Panzke]

So the server is running. I will test it with a few friends in the next few days.

./ckserver details

shows the following error message

[ ERROR ] Viewing details ckserver: Unable to detect game server.

Status: STARTED

[Panzke]

Since a short time the following error appears when running "update-lgsm":

checking GitHub module lgsm...ERROR removing module lgsm...rm: cannot remove 'lgsm': Is a directory FAIL

[h3o66]

Since a short time the following error appears when running "update-lgsm":

checking GitHub module lgsm...ERROR removing module lgsm...rm: cannot remove 'lgsm': Is a directory FAIL

strange - did not have this one time - updated the pr now to the latest release of lgsm

[h3o66]

Latest changes did add xvfb and the log setting to the PR

[github-actions[bot]]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.