Simplify first admin setup

[hennevogel]

Currently you have seed the DB with the roles and work some "rails console" magic to make a user the first admin. We should simplify that. One possibility would be to always make the user with the ID 1 Admin. Other ideas?

[differentreality]

After we create the roles, can't we also create a new person/user and set it as admin?

[hennevogel]

Sure we could but that would mean a standard user and a standard password, I would like to avoid this.

[differentreality]

Not sure what is better... Expect people to change the user/password from the seeds file or risk an unlikely yet possible situation that someone else, except for the intended person, creates the first user and gets the admin role?

[hennevogel]

Assigning admin rights to the first user seems to be the standard with webapps these days. I think we should follow it.

[gopesht]

We can create a default user with email_id:admin@opensuse.org and password:admin and set the role as admin role=3 .Then we can specify this in the documentation to login with these credentials as admin.This would simplify the first admin setup, and there won't be any need to modify the role explicitly.

[hennevogel]

@gopesht Have you read the previous comments?

[gopesht]

So to assign admin role with id 1.If that's the drill, then I can modify the pull request. I said this because I have used web apps that follow the procedure that I mentioned above.

[hennevogel]

Fixed in 5ed51c7