Docudjeex
Alternatives

Gitea

Install Gitea, a lightweight self-hosted Git service to manage your code repositories privately on your own server.
This is an alternative to Forgejo, the community-run fork created after Gitea's governance moved to a for-profit company, a concern for a project people expect to stay FOSS.

Gitea is a self-hosted DevOps platform that allows you to manage repositories much like GitHub, but on your own infrastructure.

Installation

  • /
    • srv
      • docker
        • gitea
          • data

Deploy the stack

Open Dockge, click on compose, name the stack gitea, and paste the following content:

compose.yaml
---
networks:
  gitea:
    external: false
services:
  server:
    image: gitea/gitea:1.22.0
    container_name: gitea
    environment:
      - USER_UID=${UID}
      - USER_GID=${GID}
      - TZ=Europe/Paris
    restart: unless-stopped
    networks:
      - gitea
    volumes:
      - ./data:/data
    ports:
      - 3333:3000
      - 222:22

Set your environment variables

Fill out the .env file with the required information, for example:

.env
UID=1000
GID=1000

Deploy the container and go to http://yourserverip:3333. Your Gitea instance is now up and running!

Done !

If it fails: check your firewall rules.

Exposing Gitea with Swag

The benefit of this setup is being able to access it remotely from any of your devices. To do so, we’ll expose Gitea through Swag.

Prerequisite: We assume you have created a subdomain such as gitea.yourdomain.com in your DNS zone with CNAME pointing to yourdomain.com, and unless you're using Cloudflare Zero Trust, you have already forwarded port 443 from your router to your server’s port 443 in the NAT rules.

Add Gitea's network to SWAG

In Dockge, go to the SWAG stack and edit the compose file by adding Gitea's network:

compose.yaml
---
services:
  swag:
     container_name: # ...
      # ... 
     networks:           # Connect the container to the custom network
      # ...           
      - gitea            # Name of the declared network
    
networks:                # Define the custom network
  # ...
  gitea:                 # Name of the declared network
    name: gitea_default  # Actual external network name
    external: true       # Indicates it's an external network
We assume the Gitea network name is gitea_default. You can verify connectivity by visiting the SWAG dashboard at http://yourserverip:81.

Redeploy the stack by clicking "Deploy" and wait until SWAG is fully operational.

Create the subdomain.conf file

Inside the Swag folders, create the file gitea.subdomain.conf.

✨ Tip: You can use File Browser to navigate and edit your files instead of using terminal commands.
Terminal
sudo nano /srv/docker/swag/config/nginx/proxy-confs/gitea.subdomain.conf

Paste the configuration below:

gitea.subdomain.conf
## Version 2023/12/19

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name gitea.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth (requires ldap-location.conf in the location block)
    #include /config/nginx/ldap-server.conf;

    # enable for Authelia (requires authelia-location.conf in the location block)
    #include /config/nginx/authelia-server.conf;

    # enable for Authentik (requires authentik-location.conf in the location block)
    #include /config/nginx/authentik-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable for ldap auth (requires ldap-server.conf in the server block)
        #include /config/nginx/ldap-location.conf;

        # enable for Authelia (requires authelia-server.conf in the server block)
        #include /config/nginx/authelia-location.conf;

        # enable for Authentik (requires authentik-server.conf in the server block)
        #include /config/nginx/authentik-location.conf;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app gitea;
        set $upstream_port 3000;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }

    location ~ (/gitea)?/info/lfs {
        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app gitea;
        set $upstream_port 3000;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }
}

Press Ctrl+O, then Enter to save, and Ctrl+X to exit.

Configure Gitea's domain

Now open the app.ini file from the container's file system:

Terminal
sudo nano /srv/docker/gitea/data/gitea/conf/app.ini

Then modify the server section with your domain information:

app.ini
[server]
DOMAIN = gitea.yourdomain.com
SSH_DOMAIN = gitea.yourdomain.com
ROOT_URL = https://gitea.yourdomain.com/

Press Ctrl+O, then Enter to save, and Ctrl+X to exit, then restart the container.

Done !

And that’s it! Gitea is now exposed to the web.

✨ Tip: You can protect this app natively via OIDC with Pocket ID (register it as an OIDC client), or with Authentik by following these instructions.
Contributor:Djeex

Servarr for Plex

Automate media downloads with the Servarr stack, Radarr, Sonarr, Bazarr, Prowlarr, and Overseerr for movies and TV shows.

Copyright © 2026