Skip to Content

Gitea and Forgejo for Non-Devs: Versioned Document Management for Technical Teams

Your config files deserve better than a shared folder and a "config_final_v3_FINAL.txt" file.

TL;DR: Gitea and Forgejo are lightweight, self-hosted version control platforms with an accessible web interface. They're ideal for technical teams managing config files, scripts, and infrastructure documentation: you know who changed what, when, and why. For general document management (Word, PDF, presentations), Nextcloud is still the best choice.


In this article

In most SMBs, server configuration lives in a mix of scattered text files, emails forwarded three times, and mental notes from the guy who left in December. Someone changes a firewall setting on a Friday night, it breaks something on Monday, and nobody knows what was touched.

The problem isn't that your team is disorganized. The problem is that regular file-sharing tools aren't designed to track changes line by line. An Nginx config or a PowerShell script in a shared folder is an accident waiting to happen.

There's a category of tools that solves exactly this problem. We're talking about version control platforms: software that records every change, by whom, when, and with a comment explaining why. Developers have been using these for decades. Modern interfaces make them accessible without ever opening a terminal.

Schéma : l'historique d'un fichier de configuration Diagram of a configuration file's history in a version control web interface. Four entries, newest first, each with its author and the comment explaining the change. The Friday night that broke everything has a name and a timestamp. History · firewall.conf 2 days ago, by S. R. open port 8443 for the portal 3 weeks ago, by M. T. drop a rule that was no longer needed 2 months ago, by S. R. restrict SSH access to two addresses 7 months ago, by M. T. initial version committed Who, when, and above all why: the comment is mandatory.


C'est quoi ?

Gitea and Forgejo are self-hosted web applications that run on Git, the most widely used version control system in the world: in 2022, nearly 94% of respondents to Stack Overflow's annual survey used it. In simple terms: you put your files in a repository (a structured folder), and every change is recorded with a complete history.

The web interface lets you browse files, view changes, compare versions, and even edit directly in the browser. No command line needed for everyday operations.

Forgejo was born in 2022 as a fork of Gitea, when part of the community wanted to keep the project under community governance. The two still offer roughly the same features, but each has gone its own way since 2024. More on that below.


What it's really useful for

We're not talking about replacing your Nextcloud or SharePoint here. We're talking about managing a very specific type of content: technical text files.

Think server config files (Apache, Nginx, postfix), automation scripts (Bash, PowerShell, Python), runbooks and technical procedures in Markdown, infrastructure as code files (Ansible, Terraform, Docker Compose), and network architecture documentation.

The common thread: these are all text files where every line matters, where one mistake can break everything, and where knowing who changed what is critical.


What the web interface lets you do without a terminal

This is where Gitea and Forgejo stand out from traditional command-line Git. The web interface covers everyday needs.

You can browse the file tree, just like a file explorer. You can see a file's complete history: each change is displayed with a diff (added lines in green, removed lines in red). You can edit a file directly in the browser and write a message explaining the change.

There's also a built-in wiki for team documentation, a ticket system (issues) for tracking problems and requests, and notifications to know when someone changes something.

For a technical team that doesn't want to live in a terminal, it's more than enough for daily operations.

Schéma : ce que montre une comparaison de versions Diagram of a comparison between two versions of a configuration file. Three unchanged lines give context, one removed line is marked with a minus sign, two added lines are marked with a plus sign. You see the exact line that changed, not just that the file changed. Comparison · firewall.conf listen 443 ssl; server_name portal.example.ca; - allow 0.0.0.0/0; + allow 198.51.100.0/24; + deny all; access_log /var/log/portal.log; The exact line, not just the file: that is what makes Monday morning short.


Forgejo vs Gitea vs GitLab: the comparison

All three can be self-hosted, but they don't play in the same weight class.

Criteria Forgejo Gitea GitLab CE
License GPL v3+ since version 9.0 (2024), MIT before MIT, with a paid Enterprise edition sold separately MIT (CE version)
Memory No published figure, says it needs an order of magnitude less than other forges 2 cores and 1 GB are enough for a small team 16 GB as a baseline, 8 GB at the very least
Installation Single binary or Docker Single binary or Docker Complex, multiple services
Web interface Modern, fast Modern, fast Full-featured but heavy
Built-in wiki Yes Yes Yes
Built-in CI/CD Forgejo Actions (close to GitHub Actions, not fully compatible) Gitea Actions Yes, very comprehensive
Complexity Simple Simple High
Target audience Small and medium teams Small and medium teams Large organizations

GitLab CE is an excellent product, but it's a cruise ship: its documentation sets 16 GB of memory as the baseline for a single server. For an SMB that wants to manage its configs and scripts, it's like buying an 18-wheeler to deliver pizzas. Gitea and Forgejo get the job done with a fraction of the resources.


Forgejo or Gitea: which one to pick?

In October 2022, some of Gitea's maintainers created a company, Gitea Limited, and handed it the project's domain names and trademark. Part of the community saw it as a takeover done without consultation. An open letter went unanswered, and Forgejo was launched in December 2022. Codeberg e.V., a German non-profit, holds its domain names.

For a year, Forgejo remained a version of Gitea with a few additions. In February 2024, it became a hard fork that charts its own course. In August 2024, its version 9.0 moved to the GPL v3+, a copyleft license: the code and anything derived from it must stay free. Gitea, for its part, is now backed by CommitGo, a subsidiary of Gitea Limited that sells an Enterprise edition (SAML authentication and an audit log, among other things) and a hosted offering.

For an SMB self-hosting, both get the daily job done. The difference is governance: Forgejo is run by its contributors, Gitea relies on a company that offers commercial support. Better to decide up front. Moving from Gitea to Forgejo used to be a simple drop-in replacement, but that is no longer guaranteed for Gitea versions released after the fork. At Blue Fox, we recommend Forgejo: we favour projects with community governance.


Real-world example: an IT team managing 15 servers

Let's take a typical example. Your IT team maintains 15 Linux servers: a few web servers, a database, a mail server, a firewall. Config files live all over the place: some on the servers directly, others in a "don't touch" shared folder, others in Martin's head.

With Forgejo, you create a repository per server (or a central repo with a folder per server). Every config change goes through the repo: you edit the file, write a message like "Opening port 8443 for the new reporting service," and it's recorded. When something breaks, you can see exactly what changed in the last few days and roll back in a few clicks.

Runbooks (the "what to do when X happens" procedures) live in the wiki. Change requests go through tickets. And when Martin goes on vacation, nobody's left in the dark.


Where to start

The safest way is to start small, with a single repository and a few simple rules.

  1. A modest first batch. The config files of one or two servers, or the team's procedures. Not the whole fleet at once.
  2. Messages that say why. “Fix” will mean nothing to anyone in six months. “Removed public SSH access after the audit” says it all.
  3. No secrets in the repository. Passwords, keys and access tokens go in a password vault like Vaultwarden, never in a versioned file. The history keeps everything: a password committed once stays readable in older versions, even after you delete it from the file.
  4. A backup of the server itself. The history protects against a bad change, not against losing the machine that holds it. The repository gets backed up like everything else, following the 3-2-1 backup rule.

After a few weeks, the habit sets in: before touching a server, you check the history, and afterwards, you write your line.


What it doesn't do (and that's fine)

Gitea and Forgejo aren't the answer to everything.

For office documents (Word, Excel, PowerPoint), it's the wrong tool. Git is designed for text files. A .docx file in Git works technically, but you lose all the benefits of line-by-line diffs. For that, Nextcloud with its built-in versioning is much better suited.

The learning curve is real. Even with the web interface, Git concepts (commits, branches, merge) take time to get comfortable with for someone who's never touched this stuff. Plan for some hand-holding at the start.

And if your team is small (one or two people), with few config files, it might be more than you need. A well-organized Nextcloud folder with change notes in a text file might be enough.

Our recommendation for choosing the right tool:

  1. Fewer than 5 config files and a small team: a Nextcloud folder is enough.
  2. Technical team of 3+ people with servers to manage: Forgejo.
  3. Large organization with advanced CI/CD needs: GitLab CE.


The Blue Fox position

For technical teams that need to track their configs and scripts, we recommend Forgejo. It's lightweight, installs as a single program or a Docker container, and runs on a small server. It fits naturally alongside Nextcloud : Forgejo for the technical stuff, Nextcloud for everything else.

We also support teams through adoption. Because the tool is simple, but work habits change with support, not with an email that says "here's the new system, good luck."

We help SMBs set up their version control infrastructure. Let's talk about your infrastructure


In summary

Gitea and Forgejo won't revolutionize your business overnight. But if your technical team spends time asking "who changed that" or rebuilding lost configurations, this is exactly the kind of tool that solves the problem for good. Lightweight, simple, self-hosted, and built for the daily work of teams managing infrastructure.

Let's talk about your infrastructure.


Sources

Self-hosting your own email: is it really worth it?
An honest look at self-hosted email for Quebec SMBs and non-profits