APIKeys & Monitoring - #114
Merged
Merged
Conversation
…individually getting the state, reducing load on the backend.
…nd adjust JWT generation accordingly. Defaults to 1 month if user sends a GET instead.
JacksonTheMaster
force-pushed
the
feat-monitoring-apikeys
branch
from
September 30, 2025 18:16
bf7fa2b to
9b0d914
Compare
mitoskalandiel
approved these changes
Sep 30, 2025
mitoskalandiel
left a comment
mitoskalandiel
left a comment
Contributor
There was a problem hiding this comment.
can't see any issues with this from my (admittedly limited) perspective.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a basic implementation of API keys that can be obtained from {{base_url}}/api/v2/auth/setup/apikey.
If the endpoint receives a GET, it issues an API key with one month validity.
If it receives a POST with {"durationMonths": 6}, it issues a key with six months of validity and so on. Negative values are not allowed.
This also refactors the internal serverrun check to use a global in config where applicable to reduce backend load.
This also adds a monitoring endpoint on {{base_url}}/api/v2/monitor/gameserver/status that responds with a 200 OK and json like this: {"isRunning":false} // {"isRunning":true}.