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.
decentral1se b757b806e4 chore: publish 1.3.0+1.17.2-rootless release 3 weeks ago
.drone.yml Use new image namespace 1 year ago
.env.sample Add disable_gravatar and federated_avatar 5 months ago
.gitignore Bootstrap Gitea repository 2 years ago
LICENSE Add LICENSE 2 years ago
README.md fix: point to new drone instance [ci skip] 9 months ago
abra.sh Bump app.ini version in abra.sh 5 months ago
app.ini.tmpl Add disable_gravatar and federated_avatar 5 months ago
compose.smtp.yml chore: formatting 12 months ago
compose.yml chore: publish 1.3.0+1.17.2-rootless release 3 weeks ago
docker-setup.sh.tmpl Don't run installs here 1 year ago

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 YOURAPPDOMAIN config - be sure to change $DOMAIN to something that resolves to your Docker swarm box
  5. abra app YOURAPPDOMAIN deploy

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.