The only one I think is reasonable is GraphQL. But that isn’t rest, and HTTP is just one of the transport layers it supports.

For anything claiming to be RESTful, it’s a crime.

(another pet peeve of mine is “rest” APIs that use 200 response codes for everything)

Yup, also some APIs use GET for everything. It’s a pain. And it means that filtering by verb only helps if you’re intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you’re developing the API yourself.

I think they did say that in the older thread. But for proper security, you shouldn’t have to trust them. You should have build tools that will re-fetch everything to create an identical build. That gives a clear chain of custody, which proves that morning has been tampered with.

It sounds like most, if not all, come from upstream projects.

Here’s another plug for gitea. It’s lightweight, but still has a nice feature set.

I tried hosting GitLab a number of years back, but it was more resource hungry than my host machine could handle well.

For organizing and searching the files, I’m using paperless-ngx. It’s worked pretty well for these and for scanned documents.

My issue is getting the PDFs without having to spend time every month manually downloading them.

All solutions that integrate with banking sites I’ve ever encountered were nothing more but ugly hacks, IMHO.

Yup. That’s basically what FileThis provided. A maintained set of ugly hacks to pull the files for you automatically :D.

Restic using resticprofile to configure and schedule backup runs.

Restic using resticprofile for scheduling and configuring it. I do frequent backups to my NAS and have a second schedule that pushes to Backblaze B2.

Mind sharing your Kubernetes config? I’m living off of a bunch of docker compose config files, and I’d love to make the jump to Kubernetes.