-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User Management #878
Comments
TL;DR we still have a users table, but there's only 2 rows in it: 1 for the public user, the other for admin user. |
thanks for adding this issue @awead, I like the public and admin user idea! |
now that bookmarks are factored out, i don't see a problem with the proposal. Is the reason we need a user in the first place a blacklight-ism? |
@whereismyjetpack I was just thinking that as well. Do we even need the concept of a database-backed user object? If the answer is no, then we probably don't even need Devise either. |
Interesting. If we could have anonymous sessions and rid devise, we could remove some deps and MySQL! |
Currently there are over 247 million user records in the database, all of them "guest user" accounts created by the devise-guests gem. This is because user records are created for every new session. We need to curtail these.
Proposal
current_user
for everybody (this is what we do in Scholarsphere)current_user
for admin users or other users with elevated privilegesRelated Issues
#836
#331
The text was updated successfully, but these errors were encountered: