Users

[ehharvey]

LMS will eventually support more than 1 user. We should create architecture needed to support this.

Design details

1. A DB that stores users. This DB should minimally store a username and a type (student or teacher) Just store username
2. A method of storing the active user
3. A method of changing the active user
4. Architecture needed to alter functionality based on type of current user

Todo

• Architecture Design + approval
• CLI methods of storing/changing active user (feel free to ask first before implementation :) )

[ehharvey]

@ghostp13409 I made some adjustments to the tasks here :)

One thing to note: I don't think we need to worry about the type of user just now. We should plan for roles to be in a separate table. For now, we just need userse + ability to change the user