Move sensitive settings into a separate file #5016
Unanswered
MilesBHuff
asked this question in
Ideas and Feature Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My Minecraft server, Settlescape, has its configs available on GitHub. This is used both as a handy way to track and deploy changes, and as a way for our playerbase to contribute to the project.
Sometimes, though, there are settings that aren't appropriate for a public GitHub repo: API keys, license keys, database passwords, and more.
When these sensitive settings are included in the same files as the non-sensitive settings, I am forced into an awkward situation where I have uncommitable changes in version-controlled files. It would be much nicer if these sensitive settings were placed into their own separate file, as I could then
.gitignore
it.At present, pushing changes to one of these limbo configs guarantees a merge conflict on the server during the subsequent pull. And when working on anything in the repo, I have to be very careful to not accidentally commit any sensitive settings. Neither of these is ideal.
The only sensitive setting I am aware of is the Discord token, but any others should move as well.
Beta Was this translation helpful? Give feedback.
All reactions