recipe-maintainers/recipe-maintainer
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
460eba090ba6765b05a929d32d16ca984cf66e5a
recipe-maintainer/recipe-info/gitea/setup.md
autonomic-bot f283a371bb recipe-maintainer: public snapshot (secrets + deployment plans removed, single commit) 
Sanitized single-commit public mirror of recipe-maintainer.
- Removed test-ssh/.testenv (live creds); added test-ssh/.testenv.example placeholders.
- Removed plans/ and planned-updates/ (deployment-planning docs) so no client/
  deployment domains appear in the public repo.
- All other secret stores were already gitignored.
- docs.coopcloud.tech retained as a submodule (public upstream).
2026-06-16 20:18:24 +00:00

977 B
Raw Blame History

Gitea — First-Time Setup

Prerequisites

  • DNS: gitea.<DOMAIN_SUFFIX> must resolve to the server

Steps

  1. Create the app:

    abra app new gitea --server <SERVER> --domain gitea.<DOMAIN_SUFFIX> --no-input

  2. Generate secrets:

    abra app secret generate gitea.<DOMAIN_SUFFIX> --all -m --no-input

    Save output to recipe-info/testsecrets/gitea.<DOMAIN_SUFFIX>.

  3. Deploy:

    abra app deploy gitea.<DOMAIN_SUFFIX> --chaos --force --no-input

  4. Create the first admin user:

    abra app run gitea.<DOMAIN_SUFFIX> app gitea -c /etc/gitea/app.ini admin user create \
  --username admin --admin --random-password --email admin@example.com

  5. Verify: curl https://gitea.<DOMAIN_SUFFIX> returns HTTP 200.

SSH Access (optional)

To expose Gitea's SSH service, configure Traefik to enable the gitea-ssh entrypoint and set GITEA_SSH_PORT=2222 in the app env file.