-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
CLI: Admin user should not be listed before being actually created #1448
Comments
Should be fixed in Alkarex@ae1bf1f / #1447 |
This bug is fixed. But is it necessary to set the default user at install time? Could it be possible that the default user is set at user creation time? The first created user would simply be the default one. In my opinion, this appears to be simpler. Don't you think? |
This could be an option indeed. The historical reason is that there is a global configuration (including the name of the default user) and then user-specific configurations. Furthermore, it is more consistent with the possibility to reconfigure the default user to another user. |
Historical reasons are usually bad reasons... ;-) From a user point of view, what does it change for a user to be default one or not? Is he sort of an admin? |
Historical was maybe a bad word: the situation is still the same. Yes, the default / admin user has additional rights (such as to create other users, change login type, etc.) and is also used for the content of the anonymous view. |
I still think that admin user should be the first created user and hence should not be specified at install time. It would be more consistent. An instance of FreshRSS without user cannot have a default admin user... |
When installing FreshRSS via cli, the install process creates a user whereas it should not create a user.
The user is listed but does not exist. This is a bit inconsistent.
Why not set the default user not at install time, but at user creation time ?
This make it difficult to know whether I have to really create the user or not...
The text was updated successfully, but these errors were encountered: