Use this tool for importing a Google takeout file. Follow the examples for Google photos.

https://github.com/simulot/immich-go/blob/main/docs/examples.md#google-photos-migration

This.

I found a picture with a single set of ears on the front. But the spec sheet says it weighs 50lb. Personally I’d put it on a shelf or universal rails, then use the ears to keep it in place.

Thanks for the AI tag

I’m mostly a lurker. I’ve also been selfhosting for at least a decade, and I’m a professional in the IT sphere.

I wholeheartedly support this rule change. Hardware is a big part of selfhosting/home labs. And for some people, it’s a hard leap to make.

If we end up seeing lots of redundant posts (e.g. “Can I use my old laptop to host stuff?”), we can always start an FAQ or something. But until and unless it becomes a problem, keeping the rule simple sounds perfect.

In an enterprise setting, you shouldn’t trust the server firewall. You lock that down with your network equipment.

Edit: sorry, I failed to read the whole post 🤦‍♂️. I don’t have a good answer for you. When I used docker in my homelab, I exposed services using labels and a traefik container similar to this: https://docs.docker.com/guides/traefik/#using-traefik-with-docker

That doesn’t protect you from accidentally exposing ports, but it helps make it more obvious when it happens.

I don’t know how dead it is, but it’s pretty straightforward to set up your own gateway (public or private). Even if you don’t have a tech background, there’s the “IPFS Desktop” app that stands up the IPFS service locally.

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.

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.