Bagger 288 Bagger 288

Most people in cities don’t have a garden and it’s prohibited in many places

I barely check the updates and new software sections these days, but I’m always enjoying the Weekly Highlights and the Newswire. Pretty sure I’m reading at least two of the linked post each week

Sure, you can probably build something similar with zfs snapshots, but it’ll likely not be as convenient. Have a VM? Create daily snapshots. Break something and can’t figure it out? Just reset to the last backup to a complete working state.

Personally, I have the containers’ mounts in the VMs (ergo on the nodes’ disks) and just using the NAS for the backups. Even if both Proxmox nodes catch fire I can just import the snapshot to a new one and have a working VM in the same state again. That’s a whole different level from re-cloning all the compose stacks, mount NFS shares etc. It’s the ease of use.

I use both. The main benefit of proxmox is having VM snapshots/daily backups, if you mess up, just restore the whole thing. You also have stricter isolation, e.g. put public facing containers in one VM and local only stuff in another.

Also has high availability if you have multiple nodes but that can be achieved with container orchestration as well.

The linked Fluxer article was super interesting. If the goals of federation and published posts actually get implemented, that thing is gonna be amazing. I’ll probably try it out.

The Booklore/orbit drama is weird, and I read about it the same time as I read about calibre adding an AI game to their ebook management tool (wtf). I’d have assumed more sensitive use of AI from book people, if any at all.

Oh damn

Why do you need a dedicated GPU if you don’t plan to use it anyways?

In addition to the other comments, that’s also !minilab@lemmy.world, it’s pretty dead though

Yeah, they have a great wiki, it’s how I found my stuff.

A (friend with a) 3D printer is essential. Stuff is fucking expensive on Etsy etc.

It’s a tool to manage docker stacks, e.g. by reading them from git repos. You can configure your git forge in a way to ping Komodo when something in a repo changed, Komodo then deploys the new version. You’d need your own git forge, e.g. forgejo. This is a good guide:

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

You can start without Renovate to get going, but you’ll want it sooner or later to automate checks for updates.

Good write up! Since you’re using Komodo already, are your compose stacks in git? Because if they are, check the renovate bot. It will read your files with their pinned image tags, check upstream for newer tags, and creates MRs (can also be set to auto merge) to update. Can be configured per stack.

Yeah, my #1 guilty pleasure

They are run by Autistici/Inventati which have been declared a terrorist organization by Trump, so their .org domains have been nuked (and more).

I checked as well, but the author has plenty older projects(fedilab among them) to check (I didn’t go as far, but I’d be surprised they’d actively cover tracks when they have over active repos).

That’s really promising, I have to test this

There’s some sync mode but I haven’t really looked into it yet.

Pihole is cool, but fucked me over as well more than once (not the pihole itself but the host). It’s on its own hardware now, but I plan to add a second one to reduce the single point of failure.

Lmao what a take

Yeah, found the same, just updated and everything was fine. Didn’t seem to be that breaking