#swissarmyupload — Public Fediverse posts

aww fuck, i found a bug in #SwissArmyUpload I can't reproduce in my test setup.

EDIT: It was browser caching. I was just tired

Also, @pathunstrom and I will be at #PyConUS and happy to talk about Teahouse as well as our other projects.

#TeahouseHosting #SwissArmyUpload

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.

Docs are https://swiss-army-upload.teahouse.cafe/

#TeahouseHosting

Migrated all my and teahouse's sites to #SwissArmyUpload

Hoping to get a real release before PyCon.

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)

#TeahouseHosting #SwissArmyUpload

woo https://swiss-army-upload.teahouse.cafe/ is online and it uploaded itself

(note that the docs are aspirational in many places)

#SwissArmyUpload

Pretty much all of it is "hitting feature parity with #SwissArmyUpload and then doing all the work that follows from that"

Oh hey, I have confirmation that #SwissArmyUpload and #TeahouseHosting work with #Forgejo OIDC! (iirc v15 server, v12.8 runner)

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.

Working on an excludes engine for #SwissArmyUpload

Got the first version implemented

Realized it only works for local->remote, not remote->local

🤦🏻‍♀️

OH FUCK YEAH https://github.com/AstraLuma/qwertyuiop.ninja/actions/runs/24421299970/job/71390375310

WE"RE SO BACK

#SwissArmyUpload #TeahouseHosting

Good news: #SwissArmyUpload has gotten to the point I can dog food it

Bad news: I'm finding major bugs

#TeahouseHosting

Today in #SwissArmyUpload

Turns out that pytest-ephemeral-container (that I wrote and published early in the Teahouse journey) assumes that the test suite is running on the container host, not in a peer container.

So I gotta fix that.

Unfortunately, it looks like #SwissArmyUpload is going to miss the #Forgejo v15 release.

This is the release that is rolling out full Actions OIDC support in Forgejo, allowing pipeline-based upload to Teahouse without long-lived secrets. I'm really excited to get out of the GitHub monoculture.

anyways, time to do some test engineering on #SwissArmyUpload

It largely works, but I just implemented GitHub Actions OIDC, and I can't test that locally or on Forgejo. So now I need an actual test harness.

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

this thread aside, Handtruck now has working CI/CD and a green icon.

#SwissArmyUpload #TeahouseHosting

#SwissArmyUpload update:

Recursive copy for Teahouse both up and down.

Just gotta implement GitHub oidc stuff, and it'll be ready for dogfood.

And then I can write more docs. And tests. And CI integrations. And...

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

#SwissArmyUpload got a logo, and I'm writing a user manual now.

https://codeberg.org/teahouse/stampede got a logo for its docs.

I commissioned a logo for https://handtruck.readthedocs.io/

I don't think I'm going to publish sites for SAU or Stampede until Forgejo-Teahouse happens, though. (Which is blocked on Forgejo v15, which is scheduled for late March.)

so i guess initially, #SwissArmyUpload will use just the modification time.

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.

#TeahouseHosting

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

#SwissArmyUpload #TeahouseHosting

Lunchtime check in

Integrated keyring into #SwissArmyUpload, so now it can read your username/password. Unfortunately, the 1password and BitWarden plugins for keyring both implement get_credential() badly, so I can't use them.

I'm thinking of applying for a job after lunch.

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.

#TeahouseHosting