Open V1TA5 opened 5 years ago
When we separated the frontend from the backend, we added a permission system and it was easy to grant separate permissions to specified users.
Depending on what we choose for SpaceDock, we can achieve that with Django, but that would mean an entire rewrite of the backend using Django.
no rewrites.
If its possible to implement this in the current code without to much hassle its something we should do if not leave it.
On 04/08/2019 20:28, Alexandre Oliveira wrote:
When we separated the frontend from the backend, we added a permission system and it was easy to grant separate permissions to specified users.
Depending on what we choose for SpaceDock, we can achieve that with Django, but that would mean an entire rewrite of the backend using Django.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/KSP-SpaceDock/SpaceDock/issues/211?email_source=notifications&email_token=ADMCW742BEXJNFI2LDSL4BLQC4NVVA5CNFSM4IJFCYKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3QHBYQ#issuecomment-518025442, or mute the thread https://github.com/notifications/unsubscribe-auth/ADMCW737YB4BTU2ZIVW2I6LQC4NVVANCNFSM4IJFCYKA.
With flask we could use flask-user or flask-security. The former seems to be better documented and maintained, but I used both without issues. They both use flask-login under the hood, so it should be straightforward to port to them.
Add user roles. Especialy to admin functions. (so we can have dedicated game admins or version admins). A potential Admin panel should only show the appropiate functions and have the possibillity to add/change roles to users/groups.