Hit list - Mirv/PDB GitHub Wiki
Side notes:
-
Further down the road ... perhaps we keep the user login/devise/cancancan set with a join/cross table later in development, allowing a single user login to have multiple players or multiple games they run or participate in (multi-tenancy?).
- I've have to imagine a single join/cross table with 2 foreign keys & 1 column to tell if the the relationship is the game own or participant ...
- alternatively we use a table for running game & another for participating.
- self referencing table could establish administrators too
- Both of which mean we need a user dashboard for getting a game pulled up. If its anything like that game you linked, where players can have multiple games active.
- I've have to imagine a single join/cross table with 2 foreign keys & 1 column to tell if the the relationship is the game own or participant ...
-
bcrypt? i'll open a new issue, but for now just keeping this going as I poke & discover how project is structured