#teahousehosting — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #teahousehosting, aggregated by home.social.
-
Hm, I should see how video on #TeahouseHosting shakes out
-
I need to remember to never use these terms when discussing #TeahouseHosting
-
working on #TeahouseHosting announcements
Thank you for everyone that's signed up for the mailing list.
I need to put "get a real mailing list solution" on my task list so it doesn't sneak up on me.
-
Also, @pathunstrom and I will be at #PyConUS and happy to talk about Teahouse as well as our other projects.
-
Awesome! #SwissArmyUpload v0.4.0 is out the door!
This is the first version with feature parity with the existing Teahouse actions.
Plus! This works out of the box with #Forgejo (v15)! And locally!
Available through Pip, Docker, and Actions.
-
hm, starting to think the handtruck API should be separated into "HTTP actions and concerns" (authentication, reporting errors, etc) and "meaningful s3 actions" (get object, put object, big multipart function)
-
-
I made up my todo list for #TeahouseHosting before #PyConUS next week
ope, that's a bit more than i wanted
-
RE: https://kolektiva.social/@The_Counterforce/116342559174299554
You can do this with #TeahouseHosting, too.
-
As part of the continued rollout of our noAI strategy, #TeahouseHosting is proud to announce our first human intern, Christina!
They describe themselves as "a porcupine who does code".
You can find them online at https://christina.teahouse.page/
-
Oh hey, I have confirmation that #SwissArmyUpload and #TeahouseHosting work with #Forgejo OIDC! (iirc v15 server, v12.8 runner)
-
RE: https://hachyderm.io/@MaggieFero/116473424697839218
#TeahouseHosting will happily tell you what you can do with a static site (it's a lot).
-
Hm, I think there'll be a few special upload situations for #TeahouseHosting , things like SPAs and versioned sites.
I'm thinking the way to handle these is an add-on tool to #SwissArmyUpload ? Since they're really Teahouse specific, and I'd rather SAU try to hit a middle feature set on providers, but there's a bunch of shared code.
-
@agentultra #TeahouseHosting uses zero AI and AI blocking is on our road map.
-
RE: https://floss.social/@forgejo/116414604756447118
#TeahouseHosting has been looking forward to this release for a long time!
I'm actually hoping we already support the v15 Actions OIDC, but I gotta check (and wait for Codeberg to update).
-
Things #TeahouseHosting has that are unusual:
* Support for arbitrary custom headers
* Support for arbitrary status codesThese means HTTP redirects, but also means 410/451, SPAs, setting language metadata, or other uses I haven't come up with yet
-
Good news: #SwissArmyUpload has gotten to the point I can dog food it
Bad news: I'm finding major bugs
-
```
$ curl -i http://basic.waitress.test:8314/teapot.html --resolve basic.waitress.test:8314:127.0.0.1
HTTP/1.1 418 I'm a teapot
Content-Type: text/html
Etag: "8622b9718771d75e07734684d6efa1dd"
Last-Modified: Mon, 13 Apr 2026 14:01:07 GMT
Date: Mon, 13 Apr 2026 14:02:51 GMT
Content-Length: 19I'm a little teapot
``` -
Huh, #TeahouseHosting nearly has a pattern for deploying complex SPAs.
-
Every so often I think "what if #TeahouseHosting had Gemini support"
Which would be neat
But approximately twenty people use Gemini
-
One of the tools I wish I had for #TeahouseHosting is an SSG and app for web comics
So many of them have sluggish loads
-
(For those that don't know, there's a checkbox in your Teahouse admin panel to opt-in to us acknowledging you exist and using your site for our own promotion. It defaults to unchecked, meaning we don't know you and have never seen you.)
-
Finally dug into everything and built myself an access log dashboard.
Not the same as analytics for customers, but at least I can know who's popular.
-
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.
-
RE: https://tacobelllabs.net/@astraluma/116223275384234590
this thread aside, Handtruck now has working CI/CD and a green icon.
-
I've got a few potential next features for #TeahouseHosting in mind, but I think my favorite is cookieless analytics.
Just waiting on having enough customers that we can fund something.
-
RE: https://tacobelllabs.net/@astraluma/116178925832121402
Now that #TeahouseHosting has a sign up link you should use it.
-
-
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.)
-
Yay! New version of #SwissArmyUpload out the door.
https://codeberg.org/teahouse/swiss-army-upload/releases/tag/v0.2.0
This adds git-pages support, so that I have known-good multi-backend handling.
It's still not really installable.
Next step is docs, packaging cleanup, and other things to make it maybe kinda usable.
-
milestone! swiss-army-upload v0.1 is out!
It's got none of the features I want, and it's not uploadable to PyPI because I'm using git dependencies in a few places, and I haven't tested the RPM.
But you can download it at https://codeberg.org/teahouse/swiss-army-upload/releases/tag/v0.1.0
-
Oh, #SwissArmyUpload update from yesterday:
Got all the logic for Teahouse authentication done. It's not complicated, but it did force me to straighten out my dependency injection and sort out how Teahouse's ephemeral credentials interact with Handtruck's AWS-orientated credential tools.
(Oh, and I implemented GitHub OIDC handling while I was at it, because hyperfocus.)
Next step is credentials store, because this is an user tool and I don't want to do envvars.