Configure nginx to send 2.5 clients to 2.6 lobby #11191
Merged
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 update would have NGINX (which is listening on 'prod.triplea-game.org') send 2.5 game clients to the 2.6 lobby (2.5 is the current 'main' release).
The 2.6 lobby and 2.5 game clients are compatible with each other, so this is a safe configuration update to make.
Though, 2.5 clients are currently configured to use a 'prod2' URL and they would see no difference. But, we can configure the 2.5 clients to start using the 'prod.triplea-game' server by modifying the lobby_games.yml file, which would then cause 2.5 clients to be redirect to the 2.6 lobby. Until then, this change has no impact.
Change Summary & Additional Notes
Release Note