Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TASK Add support for leaderboard as it's own microservice #77

Open
Tracked by #2
thejhh opened this issue Apr 11, 2024 · 0 comments
Open
Tracked by #2

TASK Add support for leaderboard as it's own microservice #77

thejhh opened this issue Apr 11, 2024 · 0 comments
Labels
task Issue tracking work for a task

Comments

@thejhh
Copy link
Contributor

thejhh commented Apr 11, 2024

Goal

This support technically already is on the backend side, since leaderboard is the only stateful end point in the memory game. So our current server microservice already can act as a separated microservice, if just deployed as one.

So this task is about supporting different URL for the frontend more than else. This of course could be handled with front end proxy as a devops task as well. However, frontend support might be cleaner.

@thejhh thejhh mentioned this issue Apr 11, 2024
21 tasks
@thejhh thejhh added the task Issue tracking work for a task label Apr 11, 2024
@thejhh thejhh changed the title TASK Add support to seperate leaderboard as it's own microservice TASK Add support to separate leaderboard as it's own microservice Apr 11, 2024
@thejhh thejhh changed the title TASK Add support to separate leaderboard as it's own microservice TASK Add support for leaderboard as it's own microservice Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Issue tracking work for a task
Projects
None yet
Development

No branches or pull requests

1 participant