What

I’ve seen a post on mastodon where some rsync stuff broke already :/

Is the 172. address on the same interface? Could just be some virtual docker interface being unrelated to the DHCP issue.

Yeah it’s like that in Europe. Part of it is covered by my mini photovoltaic (600Wp), but that’s not enough.

Two are fedi instances, one is “official (related to my legal name)” and mostly used for email, one for personal selfhosted stuff I want to access from outside without vpn (like this Lemmy instance), one used to be a local concert calendar which I sunset so it’s not needed anymore. Currently forgot the sixth one lol

Yearly:

• ~80€ for 6 domains (using all of them)
• 125€ electricity (480kWh, 0,26€/kWh)
• 540€ VPSes (joint projects where other admins have access, not entirely paid by myself though, still planning to migrate one of them into homelab)

Not counting ISP since we have that anyways.

I don’t know if it has side effects when there’s issues with mounting or the like.

It would also interfere if you want to unmount it and forget to disable the cronjob.

You can run mount -a to mount all fstab entries. You could put that in a cronjob I guess

Both is fine. Maintaining different datasets has the administrative overhead you mentioned, but can have security benefits, e.g. if you use different users in the different docker services and adjust the NFS permissions correspondingly. If service A gets hacked and escapes the container but doesn’t get privilege escalation, it can’t access the other services’ data.

This is independent of which version you choose, but check whether adding some storage to Proxmox is an option. Having TrueNAS as a runtime dependency for all your services can get annoying real quick.

But it claims to be.

Even if you ignore the slur, the frogs and the rune in the background: Building a chat network with proper e2ee in a few weeks doesn’t sound good. It’s clear this is made with LLMs and I wouldn’t trust it’s everyone nat all.

Here’s some offers on professional support: https://codeberg.org/forgejo/professional-services/issues

Yeah I like them as well, it’s what we use at work. The article doesn’t leave me optimistic though

It is but they’re working on federation for forgejo (which powers Codeberg).

If you don’t want to host something yourself, check codeberg

I don’t know, I’ve seen it several times mentioned in the Proxmox forum. I think it’s more of a theoretical scenario but it’s strongly advised against.

Gets annoying soon if you have more than one host. Easily automated with Ansible

You’re not supposed to run apt upgrade in Proxmox at all, it may even break your system. Use dist-upgrade.

https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates

I think they know what they’re doing, bit of a troll. Framed like this in the article:

Various entities, including some with security teams, revised their judgment about what Forgejo is and isn’t, which was the main goal of the previous blogpost.

There’s a follow up by the author:

https://dustri.org/b/follow-up-to-carrot-disclosure-forgejo.html

Including this:

So I ended up sending and email to Forgejo security team, containing: an apology, a bit about my reasoning for proceeding with carrot disclosure, recommendations about what to harden/review, and a bunch of commented exploits/proof-of-concepts as attachment. We’ll see how it goes.