I spent the last week or two configuring a CI/CD runner for #TeahouseHosting on #Codeberg, here's how I did it.

https://qwertyuiop.ninja/2026/03/16/codeberg-runner.html

I wasn't really finding in-depth documentation and blog posts, and in particular none of the published examples would build container images--the biggest limitation of Codeberg's offering.

So I fixed it.

#Forgejo

RE: https://tacobelllabs.net/@astraluma/116178925832121402

Now that #TeahouseHosting has a sign up link you should use it.

Good news, everyone!

https://teahouse.cafe/ has gained a sign up link!

#TeahouseHosting

hm, it looks like one of Teahouse's upstream providers is having A Moment. Updating user sites is affected, but not serving.

#TeahouseHosting

today in #SwissArmyUpload , got recursive download working for both teahouse and git-pages

After I get recursive upload working, I can round out some features and start dogfooding this?

(The goal is to have a usable Action in time for the Forgejo v15 release March 26, so you can upload to Teahouse from Forgejo as soon as your instance turns on actions oidc.)

#TeahouseHosting

idly looking into what it would cost to add an analytics system to teahouse

goddess below, why is it $60/region, plus _I_ have to do the replication work.

#TeahouseHosting

I admit, there's a convenient aspect to #GitPage's tarball implementation over #TeahouseHosting's S3

Doing recursive download is really easy

Ok, taking Anubis and #TeahouseHosting more seriously.

I want to block AI scrapers while allowing search engines and people goofing off through. I especially want to let things like feed readers through.

Existing Anubis deployments don't fulfill this. A casual curl is blocked. And reading through configs, the usual approach to feeds is to allow-list specific paths (which doesn't work for Teahouse).

Ok, following up on yesterday's Handtruck release, have a blog post on Codeberg and Read the Docs https://qwertyuiop.ninja/2026/02/17/forgejo-rtd.html

#TeahouseHosting