Feaure requests: unattended installation, user creation, app creation, sso, ldap integration #4423

New Issue

GiteaMirror · 2025-11-02T05:50:17-06:00

GiteaMirror commented

2025-11-02 05:50:17 -06:00

Originally created by @lukasmrtvy on GitHub (Nov 29, 2019).

Hello,
Here is my proposal to solve:

unattended installation https://github.com/go-gitea/gitea/issues/2324
default admin user creation https://discourse.gitea.io/t/i-cannot-programmatically-setup-users-in-a-docker-container/289/8
default oauth app creation https://github.com/go-gitea/gitea/issues/8764
default sso integration ( not solved here )

https://github.com/go-gitea/gitea/blob/master/docker/root/etc/s6/gitea/setup

if ! gitea migration --test; 
then
  printf 'do migration' 
  gitea migrate
fi

if [ -z $GITEA_USERNAME && -z $GITEA_PASSWORD && -z $GITEA_EMAIL ]; 
   printf 'user creation initiated' 
   if ! gitea admin get-user $GITEA_USERNAME; then
     printf 'user not found, creating new one'
     gitea admin create-user -u 
   else
     printf 'user found, modificating email and password'
     gitea admin edit-user $GITEA_USERNAME -p $GITEA_PASSWORD -m $GITEA_EMAIL
   fi
fi

if [ -z $GITEA_OAUTH2_PROVIDER_ID && $GITEA_OAUTH2_PROVIDER_SECRET ];
then
   printf 'oauth app creation initiated'
   if ! gitea admin get-app $GITEA_OAUTH2_PROVIDER_ID; then
     printf 'app not found, creating new one'
     gitea admin add-app $GITEA_OAUTH2_PROVIDER_ID -p $GITEA_OAUTH2_PROVIDER_SECRET
   else
     printf 'app found , modificating secret'
     gitea admin edit-app $GITEA_OAUTH2_PROVIDER_ID -p $GITEA_OAUTH2_PROVIDER_SECRET
   fi
fi

To do this, its needed to integrate new gitea commands:

gitea migration --test -> test if migration is done ( no need to use postgresql-client, mariadb-client, etc to check db tables are populated/migrated )
gitea admin get-user -> get gitea user ( name, password, email )
gitea admin edit-user -> edit gitea user ( password, email )
gitea admin add-app -> add oauth application ( id secret )
gitea admin edit-app -> edit oauth application ( secret )

P.S. modification commands are not necesary, its just for fully idempotent initialization of new instance. ( new gitea instance with old gitea db ). Even gitea admin auth update-oauth and gitea admin auth update-ldap exists...

Environment variables:

GITEA_USERNAME
GITEA_PASSWORD
GITEA_EMAIL
GITEA_OAUTH2_PROVIDER_ID
GITEA_OAUTH2_PROVIDER_SECRET

Something similar should be used also for oauth and ldap authentication.
There are already commands for it:

gitea admin auth add-oauth
gitea admin auth add-ldap

Would be nice to have fully integrated gitea at deploy time.

Any other ideas @lunny ?
Thanks

Originally created by @lukasmrtvy on GitHub (Nov 29, 2019). Hello, Here is my proposal to solve: - unattended installation https://github.com/go-gitea/gitea/issues/2324 - default admin user creation https://discourse.gitea.io/t/i-cannot-programmatically-setup-users-in-a-docker-container/289/8 - default oauth app creation https://github.com/go-gitea/gitea/issues/8764 - default sso integration ( not solved here ) https://github.com/go-gitea/gitea/blob/master/docker/root/etc/s6/gitea/setup ```bash if ! gitea migration --test; then printf 'do migration' gitea migrate fi if [ -z $GITEA_USERNAME && -z $GITEA_PASSWORD && -z $GITEA_EMAIL ]; printf 'user creation initiated' if ! gitea admin get-user $GITEA_USERNAME; then printf 'user not found, creating new one' gitea admin create-user -u else printf 'user found, modificating email and password' gitea admin edit-user $GITEA_USERNAME -p $GITEA_PASSWORD -m $GITEA_EMAIL fi fi if [ -z $GITEA_OAUTH2_PROVIDER_ID && $GITEA_OAUTH2_PROVIDER_SECRET ]; then printf 'oauth app creation initiated' if ! gitea admin get-app $GITEA_OAUTH2_PROVIDER_ID; then printf 'app not found, creating new one' gitea admin add-app $GITEA_OAUTH2_PROVIDER_ID -p $GITEA_OAUTH2_PROVIDER_SECRET else printf 'app found , modificating secret' gitea admin edit-app $GITEA_OAUTH2_PROVIDER_ID -p $GITEA_OAUTH2_PROVIDER_SECRET fi fi ``` To do this, its needed to integrate new gitea commands: - `gitea migration --test` -> test if migration is done ( no need to use postgresql-client, mariadb-client, etc to check db tables are populated/migrated ) - `gitea admin get-user` -> get gitea user ( name, password, email ) - `gitea admin edit-user` -> edit gitea user ( password, email ) - `gitea admin add-app` -> add oauth application ( id secret ) - `gitea admin edit-app` -> edit oauth application ( secret ) P.S. modification commands are not necesary, its just for fully idempotent initialization of new instance. ( new gitea instance with old gitea db ). Even `gitea admin auth update-oauth` and `gitea admin auth update-ldap` exists... Environment variables: - `GITEA_USERNAME ` - `GITEA_PASSWORD` - `GITEA_EMAIL` - `GITEA_OAUTH2_PROVIDER_ID` - `GITEA_OAUTH2_PROVIDER_SECRET` Something similar should be used also for oauth and ldap authentication. There are already commands for it: - `gitea admin auth add-oauth` - `gitea admin auth add-ldap` Would be nice to have fully integrated gitea at deploy time. Any other ideas @lunny ? Thanks

GiteaMirror added the type/proposal label 2025-11-02 05:50:17 -06:00

GiteaMirror closed this issue

2025-11-02 05:50:17 -06:00

GiteaMirror commented

2025-11-02 05:50:18 -06:00

@lunny commented on GitHub (Nov 30, 2019):

It's interesting. We need some new commands.

@lunny commented on GitHub (Nov 30, 2019): It's interesting. We need some new commands.

GiteaMirror commented

2025-11-02 05:50:18 -06:00

@kapsh commented on GitHub (Jul 14, 2021):

+1 for this feature, dockerised setup really could use default admin account.

@kapsh commented on GitHub (Jul 14, 2021): +1 for this feature, dockerised setup really could use default admin account.

GiteaMirror commented

2025-11-02 05:50:18 -06:00

@techknowlogick commented on GitHub (Jul 16, 2021):

In 1.14.x this is a lot more straightforward, see https://discourse.gitea.io/t/unattended-gitea-installation-from-the-cli/3373/14 for details.

@techknowlogick commented on GitHub (Jul 16, 2021): In 1.14.x this is a lot more straightforward, see https://discourse.gitea.io/t/unattended-gitea-installation-from-the-cli/3373/14 for details.

GiteaMirror commented

2025-11-02 05:50:18 -06:00

@kapsh commented on GitHub (Jul 17, 2021):

@techknowlogick this works, thanks for the hint.

@kapsh commented on GitHub (Jul 17, 2021): @techknowlogick this works, thanks for the hint.

GiteaMirror referenced this issue

2025-11-02 12:58:52 -06:00

[PR #4423] [MERGED] Disable swagger validation while it is not fixed in upstream #17367

GiteaMirror referenced this issue

2025-11-02 12:59:54 -06:00

[PR #4431] [MERGED] Disable swagger validation while it is not fixed in upstream (#4423) #17372

Sign in to join this conversation.