Lean and fast GIT server, similar to GitHub (Docker)

Since GitLab requires a relatively large amount of memory and CPU, and is also relatively slow on my NAS, I replaced GitLab with Gitea. Gitea offers a similar web interface as GitHub, is much more economical than GitLab and is more responsive. Even though the feature set is not as high as GitLab, it is perfectly sufficient for most uses.

current version 1.19.0

Docker Basics

Docker allows applications to be launched by command in a so-called container.
A container is an isolated environment independent of the operating system (OS):
When a container is first launched, Docker independently loads all the necessary sources
from the internet.
Docker can be installed on Windows, macOS or an Linux Distribution

To ensure that Gitea is can be reached securely from the Internet, I use a Let's Encrypt reverse proxy. At first I used Nginx as Reverse-Proxy, but later replaced it with Traefik. The reverse proxy provides an encrypted HTTPS connection and makes it possible to run multiple websites on one server.

Step by step Gitea and Docker including access from the internet

Hardware requirement:
  1. Almost any hardware can be used for the Docker installation: For example, a virtual server of a provider, or for home: a Mini-PC, notebook, Raspberry PI, MAC, a NAS: QNAP, Synology or any other hardware on which Windows or Linux can be installed.

Schematic representation: Access from the Internet
Internet access requirements:
  1. In the case of a rented server from a provider, the provider assigns an IP address. If you want to operate a server in your own home network, you additionally need to set up port forwarding.
  2. The access from the Internet is best done via a domain with a DNS entry to the public IP address, see Domain and its management. If you do not have your own domain, you can also use a DynDNS service to access your home network.
  3. For the certificate management and access to the web services I use a reverse proxy and Let's Encrypt certificates.
Container for Gitea:
  1. Create and customize docker-compose.yml and .env .
  2. Start container and
  3. set up


To start Gitea using docker compose, you can use the official Docker Gitea image and MySQL as database. Both images can be downloaded, created and started with a simple docker-compose.yml file. The file can be filled with any text editor as follows and then customized:

Filename: docker-compose.yml, Content: 

version: "3"
    image: gitea/gitea:1.13.6
    container_name: gitea
      USER_UID: '1000'
      USER_GID: '1000'
      DB_TYPE: 'mysql'
      DB_HOST: 'giteadb:3306'
      DB_NAME: 'gitea'
      DB_USER: 'gitea'
      HTTP_PORT: '80'
      DISABLE_SSH: 'true'
    restart: always
   #For direct test access, remove "#" in the following 2 lines. Call: http://localhost:83 or http://ServerIP:83
      #- "83:80" 

   #Labels for ReverseProxy, see: https://www.libe.net/en-traefik
      - "traefik.enable=true"
      - "traefik.http.routers.git.rule=Host(`git.domain.tld`)"      
      - "traefik.http.routers.git.entrypoints=web"
      - "traefik.http.routers.git.entrypoints=websecure"
      - "traefik.http.routers.git.tls.certresolver=myresolver"
      - "traefik.http.services.git.loadbalancer.server.port=80"
      - gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
       - "80"
     image: mysql:5.7
     restart: always
       MYSQL_ROOT_PASSWORD: 'gitea'
       MYSQL_USER: 'gitea'
       MYSQL_DATABASE: 'gitea'
       - db:/var/lib/mysql

#Without using a reverse proxy (https://www.libe.net/en-traefik) the webproxy network is likely to be missing
#and the following lines can be removed or commented out. Alternatively, the network can be created with "docker network create webproxy".
      name: webproxy

For direct access via IP address or localhost - even without reverse proxy, DNS or public IP - the commented out port setting can be activated for test purposes by removing # in front of “ports:” and -"83:80" .

For Internet access via the Traefik reverse proxythe domain must be replaced in the labels with the previously created DNS entries (in the example: git.domain.tld).

The password for the MySQL database can be stored in an .env file:



The start is done from the folder of the docker-compose.yml file with the command “docker-compose up”:

docker-compose up -d


During the initial setup on the web interface I made the following settings:

  • SSH server domain* domain.tld
  • Gitea base URL* https://domain.tld

To use Gitea purely as a private repository, I set the following in the setup:

  • Disable registration
  • Viewing requires login
  • Of course, with registration disabled, an admin user must be specified in the wizard:
    Administrator username, password, email address


New migration from the GitLab Docker container didn't work for me, but it's not so bad: after creating the repos, you can just push them from a Git folder ...

Automatic deployment of new commits

I have solved an automatic pull of new commits using webhooks. As counterpart, I have a very simple hook server in use: github.com/ncarlier/webhookd. To make sure that the commit to a specific branch is automatically picked up by a specific Docker container, I adapted the example script as follows:


# Functions
die() { echo "error: $@" 1>&2 ; exit 1; }
confDie() { echo "error: $@ Check the server configuration!" 1>&2 ; exit 2; }
debug() {
  [ "$debug" = "true" ] && echo "debug: $@"

# Validate global configuration
[ -z "$TOKEN" ] && confDie "GITEA_TOKEN not set."

# Validate Gitea hook
sec=$(echo "$1" | jq .secret -r)
if [ $sec ]; then
	[ $sec != $TOKEN ] && die "bad hook token"
	die "empty hook token"

# Validate parameters
payload="$(echo "$payload"|tr -d '\n')"
[ -z "$payload" ] && die "missing request payload"
payload_type=$(echo $payload | jq type -r)

[ $? != 0 ] && die "bad body format: expecting JSON"
[ ! $payload_type = "object" ] && die "bad body format: expecting JSON object but having $payload_type"

debug "received payload: $payload"

# Extract values
  ref=$(echo $payload | jq .ref -r)

# Pull and Reset commited Branch
 echo "branch: $branch push for $ref"
	if [ $branch != "master" ] 
		docker exec $branch bash -c "git fetch origin $branch && git pull origin $branch && git reset --hard $branch"
		echo "nothing todo: master"

In the example, the current branch is passed, and a git pull is executed in the Docker container of the same name.


For my purposes, Gitea is currently perfectly sufficient. For larger teams or more complex deployments, however, GitLab is a good choice, see also: Hosting GIT repositories yourself: Starting GitLab as a Docker containerFor easy management of Docker containers via a web interface, see also: Docker Admin Interface: Portainer Community Edition

positive Bewertung({{pro_count}})
Rate Post:
{{percentage}} % positive
negative Bewertung({{con_count}})

THANK YOU for your review!

Updated: 2023-03-23 von Bernhard | Übersetzung Deutsch |🔔

Top articles in this section

Nextcloud Server Docker | Setup + https: Let's Encrypt [ssl]

To synchronize contacts, appointments, and photos of my NAS, I tested Nextcloud and thus turned my back on other cloud providers for my private data. Thanks to Docker, the installation is easier and more flexible than ever, allowing Nextcloud to run on almost any hardware.Nextcloud Hub 4 (Version 26) releasedNextcloud Hub 4 includes numerous innovations: Improved performance, numerous new features, improved help and share options, and app improvements.

Running Bitwarden in Docker - Setup step by step

Bitwarden is a web-based password manager, similar to LastPass, but open source and the ability to run (host) it yourself. How Bitwarden compares to other password managers, I have considered on the following page: Password Managers Secure? KeePass vs LastPass vs Bitwarden. Bitwarden consists of several services, which can be provided via different containers. The relatively complex setup has been simplified with "Bitwarden Unified" especially for self-hosting by packing all services into one co...

Commissioning Zigbee2MQTT in Docker - step by step

Zigbee2MQTT is an open source Zigbee bridge which can be easily integrated into existing smart home solutions thanks to the MQTT network protocol. As an example, Zigbee2MQTT combined with MQTT broker Mosquitto and Home Assistant can collect, display, record and control data from Zigbee devices. The setup described here uses Docker as a base. Manufacturer's website: https://www.zigbee2mqtt.io

Questions / Comments

By continuing to browse the site, you agree to our use of cookies. More Details