fortify-labs / fortify Goto Github PK

Make the unit pool query usable with different aliases for units

Average MMR for Lords is required in the scaled format to assist lords in determining the quality of the lobby, while any users that are not lord need an accurate representation of their lobby average in relation to their MMR.

Lord MMR averages are also calculating inactive lords with an expected MMR of 15k, which may throw off averages due to uncertainty. Averages need to be taken purely based on known ranks/MMR

Restart the (FSM) microservice if Kafka is unreachable or a connection gets closed / dropped after successfully establishing one.

Either handle this by automatically trying to re-connect to Kafka or cause the microservice to gracefully restart.

Use this: https://github.com/Mastermindzh/react-cookie-consent
If no consent is granted, just redirect to google or so.

With the successful implementation of CronJobs fetching and storing the leaderboard to redis, the twitch bot can and should now fetch said leaderboards from redis.

This shall result in lower outbound traffic and faster response times to twitch.

See: https://longhorn.io/docs/1.0.1/snapshots-and-backups/backup-and-restore/

Listing available commands and returning descriptions for said commands.

• Recent Matches
• MMR / Rank History

Create a simple script that will only fetch the leaderboard and store it to a redis key.

• Lobby summary
• Pool viewer

This will require the historization service to store the current season id in the DB.

Refactoring in the shared library required.

DB migrations have to be created using the typeorm cli (pre-configured cli can be invoked using either "yarn typeorm [...]" or "npm run typeorm -- [...]").

Create a public player state reducer tracking currently placed and benched units for each player and then calculates the remaining units in the pool.

Keep track of placements for a particular gaming session / stream.

Implement it as either a bot command or an OBS overlay (or both).

By changing from a command based architecture to a generic event architecture, the direct commands channel become obsolete.

Going forward, having generic events will make it easier to add and remove microservices without hard coupling to specific commands channels.

When a new user logs in / signs up, create a user in the DB and migrate all matchPlayer entries to the new user.

• Rules channel
• Restructuring --> Feedback channel & help channel
• Hide unused / old channels in one category
• Create bug and feedback templates for Github and discord
• Welcome channel with basic explanations
• Discord Roles for Devs & Mods
• "Educational" Channel containing FAQ & Instructions on how to setup the GSI file
• Discord Welcome Screen

Take these numbers into consideration to interpolate adjusted mmrs: https://cdn.discordapp.com/attachments/594411917888716813/615381457967251458/unknown.png

Implement all necessary backend feature for an early 1.0.0 pilot.

Add the jobs service to build.docker-compose.yml and scripts/build.sh.

As long as GitHub doesn't fix their container registry not working with containerd (see: containerd/containerd#3291), I will be using Gitlab's image registry and CI/CD pipelines.

Once GitHub fixes their stuff, I'll reconsider wether moving back to having everything on Github is worth it.

Extend user entity object to contain field wether ToS have been accepted

Move extractor service to shared library for usage outside the bot

Create a new service that will run one-off scripts scheduled by Kubernetes CronJobs.

Add a rate limit of 2 requests per second (so 120 request per 60 seconds)

• Create own match id using a combination of the player_slot, account_id and a nonce (in case of hash collisions)
• TypeORM entities
• Match started event
• Player Final Place Event
• Match finished event

Setup HA versions of:

• Redis
• Kafka
• Postgres

Add switch (redis field with a true/false value) to disable & enable new account signups

Create a gql query and subscription to retrieve a player's pool and get newer pools pushed via a subscription in GraphQL.

Includes setting up an influx db in the local dev environment, setting up influxdb manifests for k8s and the creation of a historization service.

Write landing page descriptions for "Open Source", "Real Time Data Processing" and "Free of Charge".

Create GSI file using HTML5 (see) in browser

Add Gitleaks Github Action