kostmo
commented
5 years ago - [ ] Disk persistence: Currently, sessions are memory-backed on the server side, and restarting the server logs everyone out. It would be nice if they were persisted to disk.
- [ ] Cache github authentication: Currently, every "write" action that the user performs is preceded on the server side by a verification that the user is a member of the required GitHub org. A successful verification result should be cached on the server side.
- [x] Redirect to pre-login page (see #54): Currently, when the user attempts to perform certain actions (e.g. database writes), the frontend will reject the attempt and automatically redirect to the GitHub login. However, after the login is complete, the user is dumped on the main index page instead of the page they were on before logging in. The "referrer" page should be remembered and the user should be brought back there.
- [ ] Consistent auto-logins: Currently, not all of the actions that require a logged-in user will automatically redirect them to log in . Instead, te user is left to their own devices to find a way to log in. This would also be improved by the next point: a login link in the page header.
- [ ] Display logged-in status: This probably necessitates the use of a template renderer on the server side to propagate serverside info to the client's web page and ensure page headers are consistent.
ezyang