A painless self-hosted Git service
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Cassowary 69b3110295
continuous-integration/drone/push Build was killed Details
chore: publish 2.1.0+1.18.5-rootless release
2 weeks ago
release chore: publish 2.0.0+1.18.0-rootless release 3 months ago
.drone.yml Switch to thecoopcloud/stack-ssh-deploy 2 months ago
.env.sample feat: add forgejo overwrite 2 months ago
.gitignore
LICENSE
README.md Update abra syntax in examples (finally) [mass update] 2 months ago
abra.sh
app.ini.tmpl
compose.forgejo.yml chore: publish 2.0.1+1.18.2-rootless release 2 months ago
compose.mariadb.yml
compose.postgres.yml
compose.smtp.yml
compose.yml chore: publish 2.1.0+1.18.5-rootless release 2 weeks ago
docker-setup.sh.tmpl

README.md

Gitea

Build Status

  • Category: Development
  • Status: 3, stable
  • Image: gitea/gitea, 4, upstream
  • Healthcheck: Yes
  • Backups: Yes
  • Email: ?
  • Tests: 2
  • SSO: 3 (OAuth)

Basic usage

  1. Set up Docker Swarm and [abra][abra]
  2. Deploy [coop-cloud/traefik][cc-traefik]
  3. abra app new gitea --secrets (optionally with --pass if you'd like to save secrets in pass)
  4. abra app config YOURAPPDOMAIN - be sure to change $DOMAIN to something that resolves to your Docker swarm box
  5. abra app deploy YOURAPPDOMAIN

Create first user

Run

abra app run YOURAPPNAME app gitea -c /etc/gitea/app.ini admin user create --username USERNAME --admin --random-password --email EMAIL

See the Gitea command-line documentation for more options. Make sure not to forget the -c /etc/gitea/app.ini.

Enable SSH

You most certainly want to be able to access your repository over SSH. To do so, make sure you uncomment the right lines in the configuration for traefik.

abra app config YOURTRAEFIKAPP

There uncomment or add these lines:

GITEA_SSH_ENABLED=1
COMPOSE_FILE="compose.yml:compose.gitea.yml"

Then redeploy traefik:

abra app undeploy YOURTRAEFIKAPP
abra app deploy YOURTRAEFIKAPP

You might need to wait a bit. To check if it worked, you can run

telnet my.gitea.example.com 2222

Once you have added a public SSH key, you can check that you can connect to your gitea server with

ssh -T -p 2222 git@my.gitea.example.com

Note that gitea should be configured to listen to port 2222, i.e. GITEA_SSH_PORT=2222 in the gitea config.