Add advanced server configuration, custom launch parameters, and GHCR builds - #118
Open
KrisCris wants to merge 2 commits into
Open
Add advanced server configuration, custom launch parameters, and GHCR builds#118KrisCris wants to merge 2 commits into
KrisCris wants to merge 2 commits into
Conversation
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
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.
Summary
This PR adds more flexibility for advanced and modded Core Keeper server deployments while preserving the existing default behavior.
OVERRIDE_SERVER_CONFIGsupport that generatesServerConfig.generated.jsonat startup.MAX_NUMBER_PACKETS_SENT_PER_FRAMEandNETWORK_SEND_RATEfor network tuning.CUSTOM_LAUNCH_PARAMSfor server arguments not covered by existing environment variables.Motivation
Some dedicated-server settings—particularly network snapshot tuning and mod-specific launch flags—cannot be configured through the existing environment variables.
These changes make those settings available without requiring users to modify the container scripts or maintain a separate image. All new behavior is opt-in, so existing deployments continue to work unchanged.