[GH-ISSUE #1993] Add secrets configuration: `secrets.cfg` #1564

New issue

Closed

opened 2026-02-27 02:57:51 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 02:57:51 +03:00

Owner

Originally created by @aklin on GitHub (Aug 26, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1993

I would like to track my config directory with git, but I'd rather not compromise my Steam credentials which are stored in common.cfg.

I propose adding a new file, secrets.cfg or similar, in the same directory as common.cfg. This new file will get sourced just before common configuration. This would allow adding the secrets file to gitignore.

I tried doing this and sourcing the secrets from common.cfg, but my bash-foo isn't good enough (though there is a way I haven't tried), and I'm not sure what would happen to it after an LGSM update anyway.

I'm happy to do this myself if the team thinks it's a good idea.

Originally created by @aklin on GitHub (Aug 26, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1993 I would like to track my config directory with git, but I'd rather not compromise my Steam credentials which are stored in `common.cfg`. I propose adding a new file, `secrets.cfg` or similar, in the same directory as `common.cfg`. This new file will get sourced just before common configuration. This would allow adding the secrets file to gitignore. --- I tried doing this and sourcing the secrets from common.cfg, but my bash-foo isn't good enough (though there is [a way](https://unix.stackexchange.com/a/273348/34451) I haven't tried), and I'm not sure what would happen to it after an LGSM update anyway. I'm happy to do this myself if the team thinks it's a good idea.

kerem

2026-02-27 02:57:51 +03:00

closed this issue
added the
type: feature

Atomic
labels

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@UltimateByte commented on GitHub (Aug 28, 2018):

I see no objection as long as it doesn't interfere with regular usage and is documented in the wiki. For me, feel free to PR. @dgibbs64 any issue with this?

@UltimateByte commented on GitHub (Aug 28, 2018): I see no objection as long as it doesn't interfere with regular usage and is documented in the wiki. For me, feel free to PR. @dgibbs64 any issue with this?

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 10, 2020):

I have managed to do this. The only issue is ensuring that people understand that the secrets cfg is not encrypted or anything.

@dgibbs64 commented on GitHub (Oct 10, 2020): I have managed to do this. The only issue is ensuring that people understand that the secrets cfg is not encrypted or anything.

kerem commented

2026-02-27 02:57:51 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 29, 2022):

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

@github-actions[bot] commented on GitHub (Jan 29, 2022): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.