You can transport the cargo bike with it!

Yeah I like it a lot. Didn’t use anything else so I don’t have a comparison, but I found most things very straightforward.

It’s getting messy when you have to do non-standard tasks like removing some entries from the database

It’s been a while, but I think I used this: https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#LUKS_on_a_partition

Yes, the dual partition approach is what I usually do with LUKS

It’s not that the scale of greenhouse farming is enormous in Europe. To my knowledge, it’s mostly the Netherlands, and also “niche” crops (compared to the big ones like wheat and corn). Also my guess would be that the structures are more complicated to integrate with PV since greenhouse covers can be switched open/shut.

Europe also mostly has open farming and also usually grows crops that used to be fine with being in the sun all day. The issue is that the summers getting hotter and hotter with the climate change and they are struggling and need a lot of additional watering - or some kind of shade they didn’t need before. I’d assume that’s the same in NA.

The main difference I see between Europe and NA is how densely packed Europe is. Every square cm of land is already used for something, what’s left of natural habitats has to be protected. There’s real competition for space. Land is way more available in NA if I’m not mistaken.

Oh that’s great, thanks! It’s s bit disheartening to see how many fields are covered in PV without doing agri-pv, effectively competing with farming, at least in my area. It seems like agri pv is a purely academic thing for now, at least I haven’t ever read about productive usage. My best guess, aside from steep investment costs, would be that the laws are different for farming and pv (I’m in Germany).

I’m not sure about the no trace part, wouldn’t the higher structures need concrete foundations?

Well they targeted the biggest instance. Their attack didn’t stop mastodon as a whole, but many users were impacted

Depends on what your goal is. .social has half a million active users every month, so it certainly had some impact

Who do you mean with them?

It’s the main reason I choose them. Can’t wait to open issues on other instances without creating an account and not everything being on GitHub.

They do, it’s just a lot of work.

Here’s an example PR: https://codeberg.org/forgejo/forgejo/pulls/10380

Oof, but good to have! 💸

HA is possible with 2 (+Qdevice) with zfs repl, but I’ll look for a third one as well sooner or later. I haven’t used ceph, but everyone tells me how much of an overhead it has

What kind of distributed storage do you want to use, Ceph? What kind of orchestration/hypervisor do you use? I also have two nodes currently (Proxmox) with pseudo shared storage (zfs replication).

deleted by creator

How do you block email spam with a firewall?

Ideally, you have at least two systems, test updates in the dev system and only then allow it in prod. So no auto merge in prod in this case or somehow have it check if dev worked.

Seeing which services are usually fine to update without intervening and tuning your renovate config to it should be sufficient for homelab imho.

Given that most people are running :latest and just yolo the updates with watchtower or not automated at all, some granular control with renovate is already a big improvement.

You can configure automerge per stack and also if it’s allowed on patch, minor or major upgrades.

That or Komodo when using docker. Renovate is really good, you always know which version you’re at, you can set it up to auto merge on minor and/or patch level, it shows you the release notes etc.

This tutorial is good: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo