2.6 Work Items #12114
Replies: 4 comments
-
Map server TODO:
|
Beta Was this translation helpful? Give feedback.
-
NGINX routing Check diagram: The nginx routing allows us to send all requests to "prod.triplea-game.org" We need to set up any servers to use a context-path so that we can send requests to the right server. For the lobby, all lobby URLs then need to be prefixed with "lobby", EG: instead of "/games-listing", it needs to be "/lobby/games-listing" The routing is a mechanism that allows us to support many servers with different versions without any changes need on the client side. We are also replacing the functionality that was previously in 'servers.yaml' by having NGINX do routing for us. Specifically, previously clients fetch the 'servers.yaml' file to then determine which URLs they should connect to based on the game version. Instead of this, clients will send all requests to "prod.triplea-game.org" and NGINX will figure out the right server based on context path and the 'triplea-version' value passed in HTTP header. TODO:
|
Beta Was this translation helpful? Give feedback.
-
Game Support Server The game support server should have two endpoints, error reporting and 'latest version' TODO:
|
Beta Was this translation helpful? Give feedback.
-
Project listhttps://github.com/orgs/triplea-game/projects/2 The above project has a number of items. I think we would benefit by splitting the "TODO" between "Must-do" and "do-later". It's been a moment since I've gone through that list, IIRC most of the items are pretty valid and also track the other points raised in this discussion. |
Beta Was this translation helpful? Give feedback.
-
What is needed to launch 2.6?
Beta Was this translation helpful? Give feedback.
All reactions