For the attachments like pdf you can use webdav, but for the metadata you have to use their service [1]. They have the code repos online so it's open source, but no self-hosting instructions [2]. They claimed it to be due to technical difficulties [3], though imo they have no incentives to provide this given that they host a paid service themselves.
I'm using the podman ansible module[1] to manage the podman container atm, it's ... Okish. I wrote a spaghetti mess with ansible conditionals and loops to manage multitude of systemd files made from podman-generate-systemd. If I had some time maybe I'll try this out, a more declarative approach would certainly be nicer.
I do something similar but I don't use podman-generate-systemd; instead I create the systemd service by hand using a Jinja template[1], and then start the service[2]. This has the advantage that there's no hole where the container is running but systemd configuration has not been updated yet.
Either way, it's indeed quite tempting to use quadlet instead of the nasty templates that build the podman commandline.
I also want to check if quadlet supports override files like systemd's, because that would be quite interesting as a customization mechanism that does not require forking the playbooks.
This is new to me. I was going to run a separate DDNS for my homeserver, but given that the domain is only used in Caddy anyway, this reduce 1 place to configure stuff. Thanks
> And, depending on your economic beliefs, one could make the case it weaponizes the threat of poverty to drive that normalization.
As another commenter point out, this eerily reminds me of human organs trafficking. "People own their body, so shouldn't they be allowed to sell their organ?". We don't allow such things because this directly impacts people with low-income. Now admittedly one's organ is not comparable to one's information, but my stance on this is that privacy should be human rights, non negotiable.
Yeah, I got so frustrated with the odd workflow (having no sane way to locally test new/more advanced pipelines and having to do lot's of "change .gitlab-ci commits") at work that I started investigating alternatives.
At home, for some hobby projects, I've been using earthly. It's just amazing. I can fully run the jobs locally and they are _blazing_ fast due to the buildkit caching. The CI now only just executes the earthly stuff and is super trivial (very little vendor lock in, I personally use woodpecker-ci, but it would only take 5 minutes to convert to use GH actions).
I am not a fan of the syntax. But it's so familiar from Dockerfiles and so easy to get started I can't really complain about it. Easy to make changes, even after months not touching it. Unless I update dependencies or somehow invalidate most of the cache a normal pipeline takes <10s to run (compile, test, create and push image to a registry).
This workflow is such a game-changer. It also allows, fairly easy, to do very complicated flows [1].
I've tried to get started with dagger but I don't use the currently supported SDK's and the cue-lang setup was overwhelming. I think I like the idea of a more sane syntax from dagger, but Earthly's approachability [2] just rings true.
Not a typical use-case, but I used Fedora Server for my personal media server (Jellyfin, Nextcloud, Syncthing just to name a few) and it's been great (Though I do have to fix things occasionally since I live on the edge and auto-update every night). Since most of my service runs in Podman container, I'm contemplating switching to rpm-ostree based one like Fedora IOT, but haven't got the time to get around it yet. Used to use Silverblue for my personal laptop, but I switched to Mac M1 that I got from my job. I miss how simple and configurable Linux is compared to Mac, and if my next gig won't require a Mac I'll probably go back to Silverblue.
