These are chat archives for go-gitea/gitea
3b360b85c756 gitea/gitea:latest "/usr/bin/entrypoi..." 21 hours ago Up 21 hours 0.0.0.0:22->22/tcp, 3000/tcp demo
@jmn : A brief history of GitLab
2011: Start of GitLab
In 2011 Dmitriy was unsatisfied with the options for git repository management. So together with Valery, he started to build GitLab as a solution for this.
This commit was the very start of GitLab.
external_login_source(or something similar) and
strkOid identification is an URI, non a username. How about using an OAuth2 specific table?
strkThe rest seems good to me, beside the limit to username/password for confirmation (would prevent to associate a new oauth2 with a user created with another oauth2 or openid)
strkAnother thing: an admin might want to only delegate logins to a specific oauth prov. In which case the attach-or-register choice should not be given, forcing the "register" choice (autoregister?)
strkThe code could default to the attach tab if email is found existing. ...
strkWith pre-filled fields but still needing a submit. Isn't too annoying unless the provider is really the only auth mechanism.
strkRemember existing instances might not even have a unique email field
strkAnd I think I saw an "additional emails" table in db?
User-table should be killed