#forgejo — Public Fediverse posts

Hey @matrss, did you teach #forgejoAneksajo to update the default branch to whatever comes after anything named *git-annex on push-to-create?

I just witnessed a git annex push first creating a repo with only a git-annex branch (would previously be used as the default branch), but after it was finished, the *main* branch was suddenly the default on my forgejo-aneksajo instance! 🤯

That's really cool, so you can just `git annex push` to create a repo now, amazing! 🥳

#git #gitAnnex #forgejo

@Codeberg
How long can a migration from #Microsoft #GitHub to #forgejo at #Codeberg take?
My current migration is taking 17 hours and still working.

Used a "Token (classic)" from Microsoft GitHub.

Varnish, it's like MySQL, Gitea, ownCloud and OpenOffice?

Well we're all familiar with MariaDB, Forgejo, and LibreOffice, now one group that is likening the creation of those forks by the original development teams is also asking folks (for the sake of understanding) that #Vinyl-cache is the original, unbroken codebase that was once #Varnish, yet furthermore, is also akin to other software such as those others mentioned above both pre and post forking.

https://vinyl-cache.org/organization/on_vinyl_cache_and_varnish_cache.html#our-opinion

Obviously, this could be confusing. Which should you use? which is the original? which is better?

Honestly, this is a matter of philosophy, business, and other matters of choice; but not so much in substance - yet. These two code bases haven't had much time to diverge, but they are, and have been, for a bit now. Both are FOSS. Both (or at least one) claims to be the continuation of a two decades old code base. Here's what's important now, and how you might want to come to your own conclusions as to which one to choose moving forward.

#Sun_Microsystems manufactured some of the most admired and trusted enterprise server hardware platforms. They also created and maintained #Solaris (SunOS), and they scooped up the custodianship for what was once Star Office in the form of #OpenOffice. They also brought Monty's #MySQL into the fold, while VirtualBox was another free offering.

#Sun was acquired by the #Evil_EllisonCo, aka, #Oracle. Immediately, the company was dismantled. Servers rebranded, while the OpenOffice developer team mutinied under the tutelage of Ellison, and then departed forming "The Document Foundation (TDF) in the process - a fork, #LibreOffice resulted.

Monty Widenius, already soured on the state of MySQL's place at the table with Oracle created the fork, MariaDB (Slackware Linux was the first major Linux distro to include MariaDB as the default during installation of the OS).

MySQL had much use for Oracle but Not OpenOffice (aka OOo), and Ellison refused to give the name to the Document Foundation, so it languished in the Apache Incubator, where he had gifted it, for many years.

Another famous new name that is essentially the original team of creators and developers is #NextCloud, and yes, #ownCloud does still exist... somewhere, or so I'm told ;)

When the three people in charge of steering and the custodianship of Gitea Formed a couple of for profit companies and assigned all trade and service marks of the product to those companies, it caused a great stir within the FOSS community (because this was the de facto leading #FOSS version of a code forge especially appropriate to host FOSS projects). A new Fork, #Forgejo was birthed.

So in a nutshell, When the Varnish project bootstrapped a for profit corporation to operate under (even though at this time it's still FOSS), it likewise spawned a fork of itself, and like the others, the defecting developers created the name #Vinyl, and forked Varnish-cache so that it is Vinyl-cache that continues in the tradition of FOSS while it's expected that Varnish-cache will continue to diverge from the direction of the original code base and philosophy.

#tallship #reverse_proxy #software_forks #open_source

⛵

Boah ey jedes fucking mal wenn ich versuche, was mit #forgejo actions zu machen, komme ich *wieder* an irgendeinen Mist, der sich für mich nach einem offentsichtlichen CI-Bedürfnis anfühlt, aber nicht abbildbar ist oder vielleicht einfach nicht dokumentiert.

Heute: Repo mit sagen wir 50 Dateien. Für jede Datei will ich, wenn geändert, eine teure Action ausführen. Immer die gleiche. Sagen wir, mit LaTeX kompilieren. Aber nur die geänderten. Wie ohne für jede Datei eine eigene Action definieren?

⚙️ Imagine all #FOSS projects taking a one-week break at the same time.

🔒 No one reviewing or fixing #security bugs in #curl, the #Linux kernel, #Firefox, #Tor, ...

📦 🌑 #Codeberg and #Forgejo going dark. #Debian and #Arch mirrors disappearing. #PyPI, #npm, #crates.io, #docker. #CI pipelines stopping.

Just thinking. ❤️

Les Pays-Bas construisent leur propre GitHub pour ne plus dépendre de Microsoft.

L’État néerlandais héberge désormais son code sur une plateforme maison, 100 % libre.
La France 🇫🇷 a le même problème, mais pas la même solution 🤔

Quand un gouvernement européen décide que GitHub est un risque, la question mérite qu’on s’y arrête. Le 24 avril 2026, les Pays-Bas ont discrètement mis en ligne code.overheid.nl, une forge Git auto-hébergée, bâtie sur Forgejo, un logiciel entièrement libre. L’initiative vient de l’Open Source Program Office du ministère de l’Intérieur néerlandais. La justification relève du bon sens : l’hébergement du code source est un composant critique de l’infrastructure gouvernementale. On ne confie pas un composant critique à une entreprise soumise au droit américain.

#GitHub #Forgejo #Git #Opensource #Privacy #RegainPrivacy #BanMicrosoft #NoMicrosoft #Europe #CloudAct #DonnéesPersonnelles #SouveraineteNumerique

https://www.lsdm.live/2026/05/27/les-pays-bas-construisent-leur-propre-github-pour-ne-plus-dependre-de-microsoft/

For those trying to migrate their GitHub Pages (i.e. Jekyll SSG) to Forgejo/Codeberg Pages and struggling with the absolutely subpar documentation:

Here is the crucial snippet for your workflow YAML that makes things "just work":

- uses: actions/checkout@v5
- uses: https://github.com/actions/jekyll-build-pages@v1
- uses: actions/git-pages@v2

#github #forgejo #codeberg #pages #jekyll

Have you ever wondered if one could run #Forgejo on an #Android phone? Well, the answer is yes, and I wrote a post about it on my #blog

https://wolkensteine.codeberg.page/en/tutorials/how-to-run-forgejo-on-android/

#selfhosting #oldphone #phone #testing #fun #homelab

Have you ever wondered if one could run #Forgejo on an #Android phone? Well, the answer is yes, and I wrote a post about it on my #blog

https://wolkensteine.codeberg.page/en/tutorials/how-to-run-forgejo-on-android/

#selfhosting #oldphone #phone #testing #fun #homelab

I wonder if one can run #Forgejo on a phone ...

Let me try that.

#selfhosting #oldphone #phone #testing #fun #homelab

I wonder if one can run #Forgejo on a phone ...

Let me try that.

#selfhosting #oldphone #phone #testing #fun #homelab

#Forgejo scheint über die API keinen Zugriff auf die Logs der Actions zu ermöglichen.
Hat jemand eine Idee, wie man damit trotzdem einen automatisierten Workflow zustande bekommt, ohne sich ins Knie zu schießen?

#fedihelp @forgejo

GitHub Actions lock-in is why developers won't switch to Gitea or Forgejo despite record outages

#forgejo #git #gitea #github #microsoft #scm

https://www.makeuseof.com/github-keeps-breaking-and-almost-no-one-is-leaving-the-reason-is-one-feature/

If anybody self-host their #Git repositories via #forgejo #gitea etc, and taking any measures to protect your site from #AI crawlers.

How are you doing it? What are the options?

Thanks

New blog post: git.legoktm.com is back, sort of

https://blog.legoktm.com/2026/05/26/gitlegoktmcom-is-back-sort-of.html

You can clone (most) repositories from my self-hosted Git server again, and that's it, no web interface.

Hopefully implemented in a way that is light on server resources and minimal security exposure.

#Forgejo #Git #SelfHosting

New blog post: git.legoktm.com is back, sort of

https://blog.legoktm.com/2026/05/26/gitlegoktmcom-is-back-sort-of.html

You can clone (most) repositories from my self-hosted Git server again, and that's it, no web interface.

Hopefully implemented in a way that is light on server resources and minimal security exposure.

#Forgejo #Git #SelfHosting

New blog post: git.legoktm.com is back, sort of

https://blog.legoktm.com/2026/05/26/gitlegoktmcom-is-back-sort-of.html

You can clone (most) repositories from my self-hosted Git server again, and that's it, no web interface.

Hopefully implemented in a way that is light on server resources and minimal security exposure.

#Forgejo #Git #SelfHosting

New blog post: git.legoktm.com is back, sort of

https://blog.legoktm.com/2026/05/26/gitlegoktmcom-is-back-sort-of.html

You can clone (most) repositories from my self-hosted Git server again, and that's it, no web interface.

Hopefully implemented in a way that is light on server resources and minimal security exposure.

#Forgejo #Git #SelfHosting

New blog post: git.legoktm.com is back, sort of

https://blog.legoktm.com/2026/05/26/gitlegoktmcom-is-back-sort-of.html

You can clone (most) repositories from my self-hosted Git server again, and that's it, no web interface.

Hopefully implemented in a way that is light on server resources and minimal security exposure.

#Forgejo #Git #SelfHosting

duckduckfedi:

Forgejo/Codeberg has an option to use passkeys as an authentication factor to sign in, but weirdly I never see a prompt to store them in my password manager, they just go….somewhere.

Does anyone know how Forgejo stores passkeys?

5/N

I have a local Forgejo instance. It's not too busy at the moment.

I think I'll put some data into it tomorrow.

#Forgejo

Been less than a week, and MansionNET Git (https://git.inthemansion.com) already has 24 users and some very nice repos!

Can't wait to see more code being uploaded and mirrored, so far it's such a fun project to grow and maintain!

#forgejo #foss #privacy #selfhosted #git

3/N

I've burned more than a few hours trying to set this up. But every time Forgejo starts its setup, it changes the UID and GID of the NFS mount point so it can't write to it. I can't figure out how/why. Docker breaks all the debug tools I know how to use.

If I were smart I'd take a day off and build some LEGO.

#Forgejo #NFS #Docker

forgejo-mcp v2.24.2 is out 🎉

✨ 14 new MCP tools for Forgejo releases + attachments
🔐 Stateless per-request auth for HTTP/SSE (multi-tenant ready)
🔒️ cosign + CycloneDX SBOMs in release pipeline

Huge thanks to @byteflavour for the stateless-auth work and NixOS docs 💚

https://codeberg.org/goern/forgejo-mcp/releases/tag/v2.24.2

#Forgejo #agentic_engineering @Codeberg #agentic-sdlc

EG Social Timeline plugin WordPress: una timeline unificata per Mastodon, Bluesky, Forgejo e Diggita

https://emanuelegori.uno/eg-social-timeline-plugin-wordpress-una-timeline-unificata-per-mastodon-bluesky-forgejo-e-diggita/

EG Social Timeline plugin WordPress: una timeline unificata per Mastodon, Bluesky, Forgejo e Diggita

https://emanuelegori.uno/eg-social-timeline-plugin-wordpress-una-timeline-unificata-per-mastodon-bluesky-forgejo-e-diggita/

EG Social Timeline plugin WordPress: una timeline unificata per Mastodon, Bluesky, Forgejo e Diggita

https://emanuelegori.uno/eg-social-timeline-plugin-wordpress-una-timeline-unificata-per-mastodon-bluesky-forgejo-e-diggita/

EG Social Timeline plugin WordPress: una timeline unificata per Mastodon, Bluesky, Forgejo e Diggita

https://emanuelegori.uno/eg-social-timeline-plugin-wordpress-una-timeline-unificata-per-mastodon-bluesky-forgejo-e-diggita/

EG Social Timeline plugin WordPress: una timeline unificata per Mastodon, Bluesky, Forgejo e Diggita

https://emanuelegori.uno/eg-social-timeline-plugin-wordpress-una-timeline-unificata-per-mastodon-bluesky-forgejo-e-diggita/

@semurjengkol mangga atuh, urang kejebak kudu mindahan vm #gitlab masa lalu dulu sebelum urus nu tadi.

Cepat atau lambat eta gitlab harus urang pensiunin, mending migrasi full ka #forgejo. Jauh lebih hampang.

New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman

The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.

The filesystem is the API between CI and host.

https://blog.hofstede.it/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/

#linux #podman #containers #quadlet #devops #forgejo

New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman

The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.

The filesystem is the API between CI and host.

https://blog.hofstede.it/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/

#linux #podman #containers #quadlet #devops #forgejo

New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman

The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.

The filesystem is the API between CI and host.

https://blog.hofstede.it/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/

#linux #podman #containers #quadlet #devops #forgejo

New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman

The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.

The filesystem is the API between CI and host.

https://blog.hofstede.it/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/

#linux #podman #containers #quadlet #devops #forgejo

New blog post: Tag-Driven Deployments: How MastoSum Ships Itself with Forgejo Actions and Rootless Podman

The pipeline is tag-driven and fully automated. A git push v0.2.9 triggers a Forgejo Actions workflow that builds a UBI10-based image, cosign-signs it, and writes a trigger file. A systemd path unit picks it up, verifies the signature, pulls by digest, and restarts the four app services. No SSH, no webhook receiver, no additional daemon. The CI runner lives in the same rootless Podman user context as the app it deploys.

The filesystem is the API between CI and host.

https://blog.hofstede.it/tag-driven-deployments-how-mastosum-ships-itself-with-forgejo-actions-and-rootless-podman/

#linux #podman #containers #quadlet #devops #forgejo

2/N

Let me phrase my question differently: In that setup, where's the bottleneck? Disk I/O? RAM? CPU? Network between the hosts?

#Forgejo #HomeLab

I've got a sandbox #Forgejo instance, and I'm thinking about setting up a permanent one at home. I'm thinking about running it on a headless Raspberry Pi with the storage on a TrueNAS box, because that's what I have.

Will I regret the performance?

- Raspberry Pi 4, 8GB RAM, Docker
- 1 Gbit Ethernet
- TrueNAS on Denverton CPU, 32GB RAM, disks not SSDs.

Thanks!

#HomeLab #RaspberryPi

Quick 'n' dirty #bash script for #NixOS admin tasks that should also be useful for #Guix .
I'm pretty sure I'm not the first one to write something like this, but it was quicker to implement it than to find prior art.
But if any fellow sysadmins/selfhosters know of a standard way to do this, I'd love to know more.

Motivating example:
./enter "$(pgrep forgejo)" forgejo admin user

Should be useful for one-off #Forgejo admin tasks without having to copy the settings manually and without having to edit your system config.

https://paste.sr.ht/~raingloom/ca6b3eb624c0ad8d220bcb4b61db8cde4bbf71ba

cc: #theWorkshop

Quick 'n' dirty #bash script for #NixOS admin tasks that should also be useful for #Guix .
I'm pretty sure I'm not the first one to write something like this, but it was quicker to implement it than to find prior art.
But if any fellow sysadmins/selfhosters know of a standard way to do this, I'd love to know more.

Motivating example:
./enter "$(pgrep forgejo)" forgejo admin user

Should be useful for one-off #Forgejo admin tasks without having to copy the settings manually and without having to edit your system config.

https://paste.sr.ht/~raingloom/ca6b3eb624c0ad8d220bcb4b61db8cde4bbf71ba

cc: #theWorkshop

Quick 'n' dirty #bash script for #NixOS admin tasks that should also be useful for #Guix .
I'm pretty sure I'm not the first one to write something like this, but it was quicker to implement it than to find prior art.
But if any fellow sysadmins/selfhosters know of a standard way to do this, I'd love to know more.

Motivating example:
./enter "$(pgrep forgejo)" forgejo admin user

Should be useful for one-off #Forgejo admin tasks without having to copy the settings manually and without having to edit your system config.

https://paste.sr.ht/~raingloom/ca6b3eb624c0ad8d220bcb4b61db8cde4bbf71ba

cc: #theWorkshop

Quick 'n' dirty #bash script for #NixOS admin tasks that should also be useful for #Guix .
I'm pretty sure I'm not the first one to write something like this, but it was quicker to implement it than to find prior art.
But if any fellow sysadmins/selfhosters know of a standard way to do this, I'd love to know more.

Motivating example:
./enter "$(pgrep forgejo)" forgejo admin user

Should be useful for one-off #Forgejo admin tasks without having to copy the settings manually and without having to edit your system config.

https://paste.sr.ht/~raingloom/ca6b3eb624c0ad8d220bcb4b61db8cde4bbf71ba

cc: #theWorkshop

Quick 'n' dirty #bash script for #NixOS admin tasks that should also be useful for #Guix .
I'm pretty sure I'm not the first one to write something like this, but it was quicker to implement it than to find prior art.
But if any fellow sysadmins/selfhosters know of a standard way to do this, I'd love to know more.

Motivating example:
./enter "$(pgrep forgejo)" forgejo admin user

Should be useful for one-off #Forgejo admin tasks without having to copy the settings manually and without having to edit your system config.

https://paste.sr.ht/~raingloom/ca6b3eb624c0ad8d220bcb4b61db8cde4bbf71ba

cc: #theWorkshop

@martenlienen

This is very cool and sounds extremely powerful. With that, by making this an MCP server, you're de-facto restricting its use on non-frontier systems (ie systems with limited context due to memory).

I've found that a better approach is to follow the https://mariozechner.at/posts/2025-11-02-what-if-you-dont-need-mcp/ and replace my MCP servers with thoughtfully written skills and associated tooling, thereby reducing the memory required.

Your MCP server is fairly small as is, which is a very good thing and might make the need for the skill unnecessary, but then on the other hand, if you could reduce your MCP server to the footprint of the documentation, it sounds like a win?

This is the main skill file for my #forgejo skill, which has a huge footprint of well over tool-assisted calls (which also makes capability management a breeze)

I love @forgejo and am very happy I moved my company to it, but I do feel like the lack of a kanan tool that ties columns against queries (labels, status, etc.) is a real missing feature.

I see why they went with Projects, projects are neat, but it's not the same, and the fact the API doesn't expose a way to move cards makes Projects even less useful.

It's probably my #1 gripe about the software, and the only caveat I bring up when suggesting people move to it for work.

#Forgejo

This post originally appeared on The Fulcrum.

Welcome to this week’s The Programmer’s Fulcrum.

It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional benefit […]

This article originally appeared on The Fulcrum.

Welcome to this week’s The Programmer’s Fulcrum.

It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional […]

This article originally appeared on The Fulcrum.

Welcome to this week’s The Programmer’s Fulcrum.

It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional […]

This article originally appeared on The Fulcrum.

Welcome to this week’s The Programmer’s Fulcrum.

It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional […]

This article originally appeared on The Fulcrum.

Welcome to this week’s The Programmer’s Fulcrum.

It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional […]

This article originally appeared on The Fulcrum.

Welcome to this week’s The Programmer’s Fulcrum.

It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

As usual, we aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional […]