A painless self-hosted Git service
Go to file
Léo 975fc775c1 docs(README): how to enable SSH 2021-12-31 13:51:29 +01:00
.drone.yml Use new image namespace 2021-06-21 12:28:33 +02:00
.env.sample Fix default domain and remove STACK_NAME 2021-04-07 20:00:38 +02:00
.gitignore Bootstrap Gitea repository 2020-06-17 08:21:19 +02:00
LICENSE Add LICENSE 2020-06-17 08:30:59 +02:00
README.md docs(README): how to enable SSH 2021-12-31 13:51:29 +01:00
abra.sh Add preliminary backups 2021-11-21 21:51:11 +02:00
app.ini.tmpl Use new reverse proxy settings 2021-04-29 16:02:48 +02:00
compose.smtp.yml chore: formatting 2021-10-05 09:42:10 +02:00
compose.yml chore: release patch version 2021-11-02 21:45:37 +01:00
docker-setup.sh.tmpl Don't run installs here 2021-04-29 16:12:14 +02:00

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.