You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interaction with gorcon should be diverse and functional.
The project is not meant as a simple service delivered, configured and set running but as a full fledged solution for managing game servers.
This means, we require a sufficient way of accessing internal functionality through external interfaces, a well designed CLI being one of them.
Implementing this is blocked by #3 to offer the internal API first hand and use it with the CLI in the next step.
The CLI should be part of the gorcon binary, so no further tools are required. The user should be able to start gorcon with a single command (or as a service) and then access it through successive commands using the same binary.
This allows pretty intuitive usage of our tool and enables easy setup and change through intuitive and well known interaction.
Communication with the main process should take place through the (g)RPC API offered by #3 or the external API (skipping auth for local interaction).
For designing the client/server architecture Protobufs, gRPC and Cobra might come handy.
Acceptance Criteria:
A well designed approach to CLI layout and functionality
Use of the general API provided internally
The text was updated successfully, but these errors were encountered:
Interaction with gorcon should be diverse and functional.
The project is not meant as a simple service delivered, configured and set running but as a full fledged solution for managing game servers.
This means, we require a sufficient way of accessing internal functionality through external interfaces, a well designed CLI being one of them.
Implementing this is blocked by #3 to offer the internal API first hand and use it with the CLI in the next step.
The CLI should be part of the gorcon binary, so no further tools are required. The user should be able to start gorcon with a single command (or as a service) and then access it through successive commands using the same binary.
This allows pretty intuitive usage of our tool and enables easy setup and change through intuitive and well known interaction.
Communication with the main process should take place through the (g)RPC API offered by #3 or the external API (skipping auth for local interaction).
For designing the client/server architecture Protobufs, gRPC and Cobra might come handy.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: