Tootfinder

Opt-in global Mastodon full text search. Join the index!

@jamesthebard@social.linux.pizza
2026-04-05 18:39:41

Building containers...so much fun...
#sisyphus #devops

The docker build command continues to compile things...still have to compile Handbrake as well.
@jamesthebard@social.linux.pizza
2026-04-05 04:16:24

Version 2.0.0b5 should be the last version before the first "official" release of the client rewrite. So very, very close...lol
#programming #sisyphus

A screenshot of the 2.0.0b5 release on my personal Forgejo instance.
@jamesthebard@social.linux.pizza
2026-03-28 05:25:26

The Sisyphus client rewrite continues after a bit of a break. The `ffmpeg` module is mostly finished and should serve as a good template for `handbrake`, `av1an`, `mkvmerge`, and `cleanup` modules. Logging is progressing pretty well. The config has been expanded slightly and can now pull from TOML files on top of the standard environment variables.
#sisyphus

A screenshot of the 2.0.0a1 Sisyphus client running as it waits for an encoding job to come down the queue.
@jamesthebard@social.linux.pizza
2026-01-27 18:40:20

Wooo, now have Docker images for the `sisyphus-client`! Still not happy with the overall size of the images or how I'm versioning them, but they do make things easier to deploy.
#docker #sisyphus #encoding

A screenshot of the new Sisyphus Client image in my personal Forgejo package repository.  Even managed to get some of the LABELs right on the fourth try.
@jamesthebard@social.linux.pizza
2026-04-04 04:58:03

The long test is looking good for the `av1an`, `mkvmerge`, and `cleanup` modules, the Golang client is doing exactly what its supposed to which is a welcome change from yesterday. I need to do long tests on the `ffmpeg` and `handbrake` modules next, but I'll handle those tomorrow.
After that, I'll update documentation, release the `2.0.0` client, and deprecate the old client.
#sisyphus

The output of the `2.0.0b2` Golang client just chewing through videos with the `av1an` client.
@jamesthebard@social.linux.pizza
2026-03-22 21:31:12

A nice afternoon running some brutal encodes across the homelab. This is initial testing of the 5fist fork of the `svt-av1-psy` encoder with some pretty severe settings. Hoping that the results are worth the wait, but gotta wait until the first few results come out of the workers.
#sisyphus #av1

The server `encoder01` running an encode.  The screenshot shows the btop results of the CPU being pegged in a 24 vCPU/24 GiB RAM VM on an AMD Ryzen 9 7945HX CPU.
@jamesthebard@social.linux.pizza
2026-01-10 20:28:54

Oh yeah, this is gonna take a long while. Time to let it do its thing and enjoy some beers outside for a nice Saturday.
#sisyphus #av1 #encoding

A screenshot of the current status of all the encoding nodes from the Sisyphus front-end.
@jamesthebard@social.linux.pizza
2026-03-11 05:04:19

Now the pain in the ass part: documenting all of the routes. I think I'm gonna use Scalar because it's easy and I'm pretty lazy. Carved off the `/doc` directory to host the `openapi.yaml` and `index.html` files. So far, got one single endpoint documented...lol
#openapi #sisyphus

The `/doc` page showing the Sisyphus Server API documentation for v2.0.1.
Actually executing the GET request on the `/queue` endpoint.  The page shows the response and a ton of options that I'm kinda digging.
@jamesthebard@social.linux.pizza
2026-03-11 18:35:11

Almost 600 lines of OpenAPI documentation later and I'm done. I think I'll package the `/doc` endpoint with the Docker images since I can just copy over the static directory and have it live in the container. I'll add directions on how to add the docs to the standalone binaries as well which should cover that use case. Overall, it turned out pretty well.
#sisyphus

VSCodium showing the tail-end of the OpenAPI YAML file with the final line number being 592.
The final Scalar API docs string for Sisyphus showing all of the implemented routes.
@jamesthebard@social.linux.pizza
2026-03-14 21:23:52

Oh yeah, things are working as intended now. Unfortunately, I did crank the settings so these encodes are going to take about an hour each. However, the homelab seems to be up to the challenge.
#sisyphus #encoding

`btop` showing that the poor VM is getting absolutely destroyed being pegged at 100% CPU utilization
@jamesthebard@social.linux.pizza
2026-03-14 16:51:37

I think this might be the most frustrating thing I've dealt with: the `av1an` encoder not being able to create files in the client container. Definitely has free space, the user is running in the container as `root` (also does the this as a regular user) but absolutely refuses to run.
The mystery continues.
#av1an

Av1an encoder complaining really loudly that it cannot write the `.iwf` files to the filesystem and exiting the encode.