High Tea: Gitea with Traefik

[anon74399538]

Traefik - A reverse proxy / load balancer that’s easy, dynamic, automatic, fast, full-featured, open source, production proven, provides metrics, and integrates with every major cluster technologies…

High Tea - Self-hosted git server using Docker, Gitea, Postgres and Traefik for:

• Simple, consistent and deterministic way to create Gitea.
• Extremely flexible, powerful and self-configuring solution.
• Automatic, production-ready SSL certificates that auto-renew.

View the source

[anon74399538]

Just a quick update on High Tea (link above) for those interested. I’ve had over a month of uninterrupted and performant experience with Gitea following my last upgrade using a $5 Vultr box running Debian with Docker and Compose self-installed.

Including status code counts from Gitea reported by Traefik over the last month:

[anon74399538]

Another update on High Tea with Gitea (source linked above). This will be my last general update on stability. So far Gitea 1.5 has been running incredibly well for 30+ users and 40 or so repositories:

Server Uptime: 2 months, 1 week, 1 day, 22 hours, 24 minutes, 37 seconds
Current Goroutines: 45
Current Memory Usage: 42MB
Total Memory Allocated: 1.8TB
Memory Obtained: 607MB

Massive props to the Gitea team and those who came before for building such a stable product and suitable alternative to GitHub for those of us who want to take back control of our source code.

[anon74399538]

In the spirit of transparency I’d like to share my first hiccup with High Tea. When attempting to run my 5th Gitea backup today I found out my 25GB Vultr VPS was out of disk space. As a result, I’ve added information on how to reclaim disk space with Docker for the benefit of others here:

Managing Disk Space

If you run out of disk space while running Gitea with Docker here are some tips on reclaiming space: Run df -h --total / to check your disk space Purge or archive old backups to reclaim space Identify the size of and clean-up your Docker overlay network Run “Garbage collect all repositories” from Gitea’s Admin Dashboard Use the docker system prune -a -f to remove unused images, et cetera Look for log files you no longer need and archive and/or disable them Consider using docker-gc-cron to kee…

Additionally, here are some other resources I’ve written here which those using this Gitea with Docker will find useful as they begin self-hosting:

Manual Backups with Docker

These instructions aren’t in the documentation nor the project’s source repository so I’m jotting them down here for others. How to backup Gitea and your Gitea database using Docker adapted from the High Tea README file. Backups use the standard Gitea Backup procedure adjusted for use with Docker as follows: Shell into the Docker container: docker exec -it $(docker ps -qf "name=gitea") bash Use gitea dump the create the backup archive within the container: /app/gitea/gitea dump -c /data…

[solved] How to set up email registration

To set-up email for Gitea check out the the following email providers recommended by Discourse: Assuming you chose Mailgun do the following: Add your Gitea domain in Mailgun Add the Mailgun-suggested DNS records to domain. Rather than waiting 24-48 hours for DNS propogation look for the button inside Mailgun to check manually from the Mailgun dashboard. Edit your app.ini file to enable user registrations, email confirmations and set a noreply address. Look in the [services] section for this…

Upgrade Gitea Docker Compose

Been using Gitea for about a week under docker and so far so good. One thing which wasn’t clear to me was how best to upgrade to a new tag. I understand this will vary depending on how Gitea is installed but it would be nice to see at least some basic advice either in the documentation or on the image README itself. Here’s what I did to upgrade to the latest version, which probably wasn’t the best approach given it caused a few seconds of downtime: docker-compose pull gitea docker-compose down…

Here are the sizes of my back-ups, which I’m simply going to offload to another server as they’re unnecessary on the gitea production vps I use to run git.habd.as:

-rw------- 1 user docker 252M Jul 16 07:22 gitea-dump-1531725738.zip
-rw------- 1 user docker 1.2G Sep 24 08:41 gitea-dump-1537778440.zip
-rw------- 1 user docker 2.6G Oct 12 08:19 gitea-dump-1539332248.zip
-rw------- 1 user docker 2.8G Oct 17 12:02 gitea-dump-1539777559.zip

Total repository count is 56 at current, many of which are mirrors of kewl security software I found on GH.

[anon74399538]

6 months of uptime and the $5 debian vps used to run Gitea with Traefik continues to chug along.

The Gitea database holds 49 users, 2 organizations, 2 public keys, 95 repositories, 97 watches, 7 stars, 10269 actions, 51 accesses, 196 issues, 696 comments, 0 social accounts, 2 follows, 65 mirrors, 3713 releases, 1 authentication sources, 0 webhooks, 7 milestones, 67 labels, 0 hook tasks, 2 teams, 0 update tasks, 72 attachments.