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
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The text was updated successfully, but these errors were encountered: