DATABASE · BACKEND · ELO

Segfault Database

The business logic and inbetween for my database and my apps which use it. Simple restful API

This is the middleman between applications using my servers for say storing stats and whatnot or checking if users are subscribed to vip, and the backend databases actually storing said information, or the rest api for the donation platoform itself. Goals of this are to be efficient and async, secured with seperate auth tokens for each server contacting this service for info, and ideally this should also be stateless to allow for later use of something like kubernetes.

TODO - Implement connection to database - connect with paddle rest api - create rest api for applications using my service - stats access api - additional stats endpoints for index-based or discord - endpoint for getting top ranked players - vip check api - secure tokens identifying each server/app that can access my service for authentication - admin accounts associated with specific server tokens - Secure and Lock down the api with either NGINX or inside actix - discord bot functionality - start a bot - connect bot to api - add functions for linking accounts - [ ] create service config for running app on our server - [ ] create nginx forwarding configuration

  • Database
  • Backend
  • ELO
segfault_database0 ★

The business logic and inbetween for my database and my apps which use it. Simple restful API

  • .cargo
  • migrations
  • scripts
  • src
  • .env
  • .gitattributes
  • .gitignore
  • Cargo.lock
  • Cargo.toml
  • README.md
Databasebranch: master