-
Notifications
You must be signed in to change notification settings - Fork 470
set admin user from a rake task and disable first-user is admin #314
set admin user from a rake task and disable first-user is admin #314
Conversation
I've set false as default because it is the safest option, but it breaks backward compatibility ... is it ok? |
@@ -39,3 +39,14 @@ ldap: | |||
guess_email: | |||
enabled: false | |||
attr: "" | |||
|
|||
# Set first_user_admin to true if you want that the first user that signs up | |||
# becomes the admin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Set first_user_admin to true if you want that the first user that signs up to be an admin.
yeah, I'm a bit sceptical about breaking the compatibility. I wouldn't do it |
Same here, default to true. Moreover, the config file is wrong, you should follow the current convention. It should be like this: # Set to true if you want that the first user that signs up to be an admin. If
# this is false, then you will need to perform the following command to set the admin user:
# $ rake portus:set_admin
first_user_admin:
enabled: true Then, when checking about this in the Ruby code, you write: APP_CONFIG["first_user_admin"].enabled? In fact, you can do this check inside the .slim file, there's no need to declare the |
Oh, and by the way, could you update the Changelog ? |
does it look good now :) |
# rake portus:set_admin | ||
# in order to set the admin user | ||
# | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
empty line not needed
LGTM 👏 Just fix my nitpicks and put everything into one commit ;) |
+1 |
set admin user from a rake task and disable first-user is admin
fixes #313 Signed-off-by: Jordi Massaguer Pla <jmassaguerpla@suse.de>
fixes #313