homelab/druid/config/gitea
Joey Hafner 05e2d2b754
All checks were successful
Deploy to Fighter / Deploy-to-Fighter (push) Successful in 4s
Deploy to Druid / Deploy-to-Druid (push) Successful in 5s
Update "internal" label to "fighter"
2024-02-13 21:15:32 -08:00
..
.env Init Gitea on druid 2023-11-23 13:29:21 -08:00
docker-compose.yml #120 Split config yaml 2024-02-12 23:34:48 -08:00
gitea.env Init Gitea on druid 2023-11-23 13:29:21 -08:00
README.md Update "internal" label to "fighter" 2024-02-13 21:15:32 -08:00
runner_config.yaml Init Gitea Runner 2024-02-12 14:29:48 -08:00
runner-dind.env Add host labels to gitea runners 2024-02-13 10:53:03 -08:00
runner-ubuntu.env Add host labels to gitea runners 2024-02-13 10:53:03 -08:00

app.ini Snippets

The main Gitea config file is located at ~/data/gitea/gitea/gitea/conf/app.ini.

Configure connection to postgres DB container.

[database]
PATH = /data/gitea/gitea.db
DB_TYPE = postgres
HOST = postgres:5432
NAME = gitea
USER = gitea
PASSWD = [Located at postgres_secrets.env]
LOG_SQL = false
SCHEMA = 
SSL_MODE = disable

Disable OpenID as login option.

[openid]
ENABLE_OPENID_SIGNIN = false
ENABLE_OPENID_SIGNUP = false

Allow migrating from specific domains.

[migrations]
ALLOWED_DOMAINS = gitlab.jafner.net, *.github.com, github.com

Re-register Gitea Runners

To force the runners to re-register (to apply updated labels, for example).

  1. Stop and remove the containers. Run docker ps -aq --filter name="gitea_runner-*" | xargs docker stop | xargs docker rm.
  2. Delete the .runner files for each runner. Run find ~/data/gitea/ -name ".runner" -delete.
  3. Bring the runners back up. Run docker compose up -d from the gitea directory.