feat(command) adds a command to place the systemd service file in the right location

[legendofmiracles]

This PR adds a command to generate a systemd service file and places it in the /etc/systemd/system, so that the user can easily enable a gameserver upon boot, without having to write his/her own service file.

Why only systemd?

Because all the official supported distros use systemd and most distros in general as well. If people request other init systems, i'd glady add support for those aswell.

• [x] New feature (change which adds functionality).

Checklist

• [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

EDIT: I opened a Pull request: https://github.com/GameServerManagers/LinuxGSM-Docs/pull/54

Showcase

(the last information text, prints "the game" instead of this)

[h3o66]

Maybe you could squash/rebase the commits to one and do a commit title that matches the "Semantic Pull Request" standard. More info can be find in the dev docs: https://dev-docs.linuxgsm.com/getting-started/branching#pull-requests

Branching and Pull Requests

[legendofmiracles]

Is this better?

[h3o66]

Is this better?

looks good to me

[legendofmiracles]

I added documentation: https://github.com/GameServerManagers/LinuxGSM-Docs/pull/54

[dgibbs64]

Also this will need to link to an issue and docs will need to be updated.

[legendofmiracles]

@dgibbs64 this PR links to an issue: and i have also provided a update for the docs: https://github.com/GameServerManagers/LinuxGSM-Docs#54 (probably also riddled with spelling mistakes - english is not my native language)

[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.