# Gitea Gitea is an open-source, self-hosted Git platform for code hosting, code review, project management, packages, and CI/CD. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Gitea v1.27.3 Ships 18 Security Hardening Fixes DevFeed: [Gitea v1.27.3 Ships 18 Security Hardening Fixes]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-09-01T06:31:36Z Content type: article Language: en Sources: [Self Host Lab]() Topics: [Gitea](), [Security](), [Authorization](), [API](), [Vulnerabilities](), [Pull Request](), [GitHub](), [GitLab](), [Maven](), [Swift]() Tags: [api](), [changelog](), [code](), [git](), [gitea-v1-27-3-ships](), [github](), [maintainers](), [network-security](), [network-security-news](), [news](), [pull-requests](), [release](), [security](), [vulnerabilities]() ### AI overview Gitea v1.27.3 introduces 18 security hardening fixes focused primarily on access control. The release narrows package and API-token access, restricts repository and attachment exposure, strengthens pull-request and artifact trust boundaries, and limits several migration and metadata inputs. It follows earlier Gitea releases that addressed numbered vulnerabilities, but these fixes do not carry dedicated CVE identifiers. ### Source excerpt Gitea v1.27.3 landed August 29, 2026 with an unusually long SECURITY section: 18 separate access-control hardening fixes, none carrying a CVE identifier. The changes tighten package API scope, attachment paths, repository enumeration, and more. It's the third Gitea security story here in three weeks, following the CVE-2026-59774/60004 patches and CISA's active-exploitation confirmation. Update on your normal schedule. ## Gitea RCE Flaw Now Under Active Exploitation, CISA Confirms DevFeed: [Gitea RCE Flaw Now Under Active Exploitation, CISA Confirms]() Original publisher: [Read original article]() Author: Christian Rakoot Published: 2026-08-29T06:33:49Z Content type: news Language: en Sources: [Self Host Lab]() Topics: [Gitea](), [Vulnerabilities](), [Security](), [incident](), [Cryptocurrency](), [Docker Container]() Tags: [cryptocurrency](), [docker-container](), [gitea-rce](), [hosting](), [incident](), [network-security](), [network-security-news](), [news](), [security](), [self-hosted](), [vulnerabilities]() ### AI overview CISA confirmed that the critical Gitea vulnerability CVE-2026-60004 is being actively exploited and added it to the Known Exploited Vulnerabilities catalog. The article explains the exploit through Gitea's diffpatch API, which can enable arbitrary code execution, and describes a documented compromise of an outdated self-hosted instance that led to cryptocurrency mining inside a Docker container. ### Source excerpt CISA has added CVE-2026-60004, the critical Gitea RCE flaw patched in version 1.27.1, to its Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild. Help Net Security documented a real compromise: an outdated instance with open registration hit by an automated scanner, ending in a cryptocurrency-mining payload. Here is what changed and how to patch. ## Setting up local Codeberg runners DevFeed: [Setting up local Codeberg runners]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2026-03-02T18:29:02Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [CI/CD](), [Docker Compose](), [Docker](), [Gitea](), [Command-line interface](), [configuration](), [container]() Tags: [article](), [ci](), [ci-cd](), [cicd](), [coding](), [community](), [configuration](), [container](), [development](), [docker](), [engineering](), [guide](), [how-to](), [inclusive](), [opensource](), [software](), [terminal](), [workflow]() ### AI overview This tutorial explains how to set up a local CI/CD runner for Codeberg. It covers registering the runner, configuring and launching a Docker-based runner with Docker Compose, and choosing between the containerized and direct binary methods, including considerations for Mac computers with Apple Silicon and Android builds. ### Source excerpt In my previous article, First steps towards Codeberg, we looked at how to get set up and comfortable on the platform. Now that your code has a new home, it's time to level up your workflow with automation. While Codeberg provides shared runners for CI/CD, there are plenty of reasons to run your own, among others, performance specific hardware requirements avoiding queue times In this guide , I'll show you how to use your local machine as a CI/CD runner for Codeberg. This works behind firewalls and home routers without needing to expose your IP address. Sounds cool, right? Depending on your needs, you can choose between two setup methods: the containerized approach using Docker / OrbStack, or running the act_runner binary directly. Since I am on a Mac with Apple Silicon, the choice actually matters quite a bit. Docker on M-series chips runs Linux ARM64 images, and unfortunately, the standard Android build tools don't officially support that environment yet. If you are here for Android builds, you might want to look at the binary method; otherwise, Docker is a safe bet. First, get your registration token. On Codeberg, navigate to Settings > Actions > Runners Click Create new runner Copy the Registration Token Next, prepare the workspace. Docker / OrbStack Open your terminal and create a folder to house the runner's identity and configuration. mkdir codeberg-runner cd codeberg-runner After that, create the configuration by putting a file named docker-compose.yml in that folder: code docker-compose.yml Here's how that file should look like. Replace and with your registration token and a name for your runner. will appear in the Codeberg dashboard. services: runner: image: gitea/act_runner:latest container_name: codeberg_runner restart: always environment: - GITEA_INSTANCE_URL=https://codeberg.org - GITEA_RUNNER_REGISTRATION_TOKEN= - GITEA_RUNNER_NAME= - ACT_RUNNER_DEFAULT_IMAGE=gitea/runner-i ## Gitea: monta tu propio servidor Git DevFeed: [Gitea: monta tu propio servidor Git]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-08T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Gitea](), [Git](), [forgejo](), [GitLab](), [Linux](), [Go Language](), [nginx](), [PostgreSQL](), [systemd](), [let's encrypt](), [MariaDB](), [SSL]() Tags: [forgejo](), [git](), [github](), [gitlab](), [go](), [let-s-encrypt](), [linux](), [mariadb](), [nginx](), [postgresql](), [ssh](), [ssl](), [systemd]() ### AI overview A Spanish tutorial explains how to install and configure Gitea as a lightweight, self-hosted Git server. It compares Gitea with GitLab and Forgejo, then covers system setup, databases, systemd, Nginx, SSL certificates, repositories, and SSH access. ### Source excerpt Instala y configura Gitea como alternativa ligera a GitHub o GitLab para alojar repositorios Git en tu propio servidor. ## First steps towards Codeberg DevFeed: [First steps towards Codeberg]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2025-12-31T11:43:33Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [Open Source](), [hosting](), [forgejo](), [Gitea](), [GitHub](), [bitbucket](), [passwords]() Tags: [article](), [bitbucket](), [coding](), [community](), [development](), [digitalsovereignty](), [engineering](), [forgejo](), [gdpr](), [git](), [github](), [hosting](), [inclusive](), [open-source](), [opensource](), [privacy](), [software]() ### AI overview An introductory tutorial about Codeberg, a community-driven, nonprofit platform for hosting software projects. The author explains its open-source, privacy-focused model and demonstrates registering an account and beginning to migrate a GitHub repository. ### Source excerpt A lot of Europeans are currently talking about Europe having to become more independent from US-based big tech. Being a European myself, I feel the need for this, too. However, just talking won't make a difference. So, why not make this our New Year's resolution? Here's mine: I love open source. Given GitHub's recent trajectory toward centralisation, I feel there are better-suited homes for my repositories. That's why I will start migrating them to Codeberg. What is Codeberg? Codeberg is a community-driven non-profit platform for hosting software projects. Many consider it the leading independent alternative to commercial services like GitHub and Bitbucket. While it looks and feels very similar to GitHub, its underlying philosophy and legal structure are fundamentally different: unlike GitHub, which is owned by Microsoft, Codeberg is run by a German non-profit organisation called Codeberg e.V.. It is funded by donations rather than venture capital or ads. The platform runs on Forgejo, which is a community-governed fork of Gitea. Therefore, the very software used to run the site is itself open source and transparent. And it is privacy-focused. Since Codeberg is hosted in the European Union (Germany), it adheres to strict GDPR standards. It does not track users for advertising and avoids black box AI features like GitHub Copilot. Does this sound appealing? To me it certainly did. That's why I decided to jump right in. In this introductory article, I'll show you my first baby steps, that is, registering and migrating the first GitHub repository. Signing up Registering is a very quick and pleasant experience. Visit https://codeberg.org, find and click the Register button. Just enter a username, your email address, a password, and the randomly generated number or word. Once you click on Register Account, you should receive an email with the inevitable confirmation link. Click on the link to verify your email address. You will be directed to your personal Codeberg landing ## Migrating from Gitea to Forgejo the long way DevFeed: [Migrating from Gitea to Forgejo the long way]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2025-09-01T14:02:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [forgejo](), [Gitea](), [migration](), [PostgreSQL](), [SQLite](), [Zip]() Tags: [forgejo](), [forgejo-migration](), [gitea](), [github](), [github-alternative](), [github-copilot](), [migration](), [postgresql](), [sqlite]() ### AI overview A firsthand account of migrating a Git server from Gitea to Forgejo. The author describes why a direct instance migration no longer worked, the risks of an attempted upgrade, and later approaches involving account-by-account migration and database dumps. ### Source excerpt With the renewed interest in Forgejo I decided to finally pull the plug on moving out of Gitea, and this is how it went. ## Building The Roottrees are Dead DevFeed: [Building The Roottrees are Dead]() Original publisher: [Read original article]() Published: 2025-01-27T00:00:00Z Content type: tutorial Language: en Sources: [Robin Ward]() Topics: [Game Development](), [Godot](), [Homelab](), [Linux](), [Gitea](), [Docker](), [Git](), [Windows 11](), [tailscale](), [blender](), [Synology]() Tags: [diskstation](), [docker](), [game](), [game-development](), [git](), [gitea](), [homelab](), [linux](), [tailscale](), [windows]() ### AI overview The developer describes the technical considerations behind building the Steam version of The Roottrees Are Dead. The supplied excerpt covers the game's release and reception, a homelab using Linux, ZFS, Gitea, Docker, and Git LFS, backup practices, remote access through Tailscale, and development hardware. It also identifies Godot as the game's engine. ### Source excerpt The Roottrees are Dead was released on January 15, 2025 and it did much better than I ever expected. The reception has been amazing. In just over a week, the game hit the magic mark of 500 reviews on Steam, and triggered the "Overwhelmingly Positive" status. On BlueSky, Bloomberg writer Jason Schreier blew me away when he posted: "Seven days into 2025 and I've already played what I suspect will be one of my favorite games of the year: The Roottrees Are Dead." Wow!