If I had a Nickel for every time ive had to fight to get docker working inside a ci/cd pipeline for a project this year, well... I'd have two nickels.

Which isnt a lot but its strange that its happened to me twice.

We’re thrilled to announce the first release candidate (RC0) of Gitea 1.24 is now available!
Check out what’s new and give it a try:
https://blog.gitea.com/release-of-1.24.0-rc0/
#Gitea #Git #DevOps #OpenSource

So far so good, #gitea server for #qwan up for a week. Transferring 152 git repositories was a bit of a faff, but now it is easy to share our work. (or work in progrss - https://gitea.apps.sustainabledelivery.com/ . 'explore' gives you the first open repo. I like the focus on energy efficiency on the default homepage ).

Seriously thinking about ditching my #selfhosted gitlab for #forgejo due to performance issues. #gitea could also be an option.

LLM scraping bots vs FOSS Git Platforms

https://www.youtube.com/watch?v=dgNL7aztM3o

Spent more time than I’d have liked trying to work out how to get docker builds working inside Forgejo actions. I’ve added my notes to my digital garden. https://notes.jamesravey.me/Software/Forgejo#docker-in-docker

#docker #softeng #gitea #forgejo (https://brainsteam.co.uk/notes/2025/04/28/1745828299/)

Dal momento che sono stufo delle minchiate dell bigtech a proposito dell'IA, ho deciso che tutto ciò che ho su #GitHub sarà trasferito su #Gitea , e questo grazie ai @devol che tengono in piedi *anche* questo servizio.
Approfitto per mostrare una schermata di #LazyGit , un client #git fantastico!

Small step for #DigitalSovereignty . Migrated #QWAN 's 152 git repositories to a self-hosted #gitea (after #bitbucket demainded money. we don't need issue trackers etc, so even gitea is overkill. I rarely use the web ui of these things, only to search a repository and clone it). h/t #dokku for making the first steps easy and @berthub.eu.articles for raising awareness.

#kompot #selfhosting collective finally made a move to switch over from #gitea to #forgejo

sysadmins @g1smo, @testman and @shtumf described a process as very smooth with a sole problem of a wrong last updated date on all of the projects.

We had this planned since the fork, we were following the process closely and stood firmly on forgejo side. We're still a few versions behind the latest. A big server update is planed for May, if we will manage to summon up the community

GitHub & GitLab sind dir zu groß, zu closed oder zu teuer?
Dann schau dir Gitea an – eine schlanke, self-hosted Open-Source-Alternative, die alles mitbringt, was du brauchst: Repos, Issues, CI/CD, und das komplett unter deiner Kontrolle.

In meinem neuen Blog zeige ich, warum ich Gitea nutze & wie mein Setup aussieht

https://www.marcogriep.de/posts/gitea-die-open-source-self-hosting-alternative-zu-github-und-gitlab/

Woke up this morning to yet more Linode alerts and another failed server as a result of AI bots relentlessly scraping my #Gitea instance.

I heard about #Anubis (https://anubis.techaro.lol) when Xe Iaso (https://xeiaso.net) was on a recent episode of the #SelfHostedShow podcast and so it seemed like a great opportunity to give it a try. I don't really need "SEO" or any discoverability on Gitea, so hopefully the only downside is that new visitors need to wait a few secs before things load

Gitea v1.23.7 Released: https://github.com/go-gitea/gitea/releases/tag/v1.23.7
#linux #linuxgaming #update #foss #release #gitea #git #selfhosted

Gitea 1.23.7 is out now!

This important update includes essential fixes and improvements—upgrading ASAP is highly recommended for all users!

More details: https://blog.gitea.com/release-of-1.23.7/

GitNex 8.0.3 is out with fixes for a few bugs that affect all users. Update when you can. :)

- Fix offline cache affecting online activities
- Fix glide for self-signed certificates

https://codeberg.org/gitnex/GitNex/releases

Doing some research on #LLM #bot protection for our selfhosted services. We had multiple downtimes per week for last few months mostly due to crawlers DDOSing our #gitea service which brought the whole server to its knees (running more than 15 web services). It would be nice to hand out invoices for our devops work...

Anyways #askFedi what kind of protection would you recommend? We're opting for solution that's quick and easy to implement and lightweight.

Hm... so this new AI thing from @gitea ... it's definitely interesting, and many people aren't reading, again.

So, what did they do?

They basically created an API client that is usable for LLMs - meaning that LLMs can now directly interact with Gitea. It's not integrated into the server by itself, and nobody is required to use it. Basically, it's HTTP MCP. It's like an API client for a programming language. So it's not a bad thing in itself.

Also, this client by itself doesn't crawl other sites / uses data that was crawled from other sites, since it's literally just an API client.

BUT (!) you have to use an existing LLM model using a client (e.g. Cursor) to be able to use this API client. Now that's the interesting part... I don't know if there's actually a good LLM that only learned from data that it was allowed to use. This means, that Gitea kind of promotes using LLMs that crawled people's sites without their permission.

Sadly, the screenshots shown in the blog post by Gitea don't show what model they are using, so we can't tell if they are using a good or a bad model. (Though, I'm not sure if we specifically need to know that in this case.)

Anyway, I'm always happy to see people switch to @forgejo. I, personally, used it almost since I started moving away from GitHub / -Lab and I love it. Sadly, I know a few people who can't yet move to Forgejo since they're using architectures that Forgejo doesn't build for docker yet.

For those people who are still angry and "need to" be aggressive towards the devs: Calm down, maybe read my blog post that I made in collaboration with Finnley about outrage (https://steffo.blog/outrage-warps-reality/) and have a great day. Maybe go for a walk outside?

Anyway, have a lovely day!