Ah, nice. In that case just beware to move /var/lib/private/conduwuit to /var/lib/private/continuwuity, not /var/lib/conduwuit to its counterpart

Ah crap, forgot to ping you! Sorry!!

Yep, easy decision now. Migration went smoothly, just had to move the state dir and chown it to continuwuity:continuwuity. Might be different on docker though, no idea, sorry 😄

Update: seems to me tuwunel is drama waiting to happen. See updated post for details.

Yes, completely agree. It seems that the matrix foundation could easily take a different path to allow the community to flourish and third-party servers to have a much easier time. Since I’m not federated, I wouldn’t even mind if whatever fork I’ll end up on eventually says “fuck this, we’re not following synapse specs any more”.

But yeah, I am sure selling premium accounts on matrix.org is what will save the matrix ecosystem… 🤦🏼‍♀️

Understandable.

There’s nothing technically wrong with it, it’s just a glacial development speed. I tried contributing there myself when I wanted a specific feature (which had been requested years prior by someone else and was deemed a good idea), it took months before I even got a single comment back.

In the meantime, I had switched to conduwuit because it was a much, MUCH more active project. However, conduwuit has diverged substantially from conduit, including irreconcilable database changes, so it is not possible to migrate back, that would require starting from a fresh slate and loosing all user data.

Nice, how’s it been going?

Roger, will do.

Yeah, community driven sounds like unless there’s new drama. But yeah, currently tending towards continuwuity. Purely vibes based from snooping around both repos.

Not sure, but they also support Borg, which definitely does.

Btw, nice read OP. Always great to see more Nix “in the wild”.

Yeah, but no dark magic involved.

• build image
• copy to proxmox ISO store
• import, resize disk
• start, wait to come online
• read ssh pubkey, save it
• rekey secrets
• rebuild VM

The only “magic” parts are two nix modules for handling proper networking and hardware setup, and exposing required attributes to the script.

Works really well, zero manual config (beyond the services you want to run…) required on nix or proxmox side.

Nothing. People fearmonger

Funny - same thing here. Got 3 proxmox hosts running, all virtual machines are NixOS though.

I’d love to go full Nix, but between my GF and I, we kinda split the responsibilities: hardware is hers, applications are mine. And there’s not a chance she’ll give up her Proxmox hosts 😄

Got it automated to a single “provision” command though that will spin up any of my nix VMS unanttended, so I’m happy with that.

Last place of employment had develop as the default branch. Actually quite liked it. (There also was a main branch, which only got merged into as part of the release flow, so might as well have called it release, I suppose).

Anyway, IMO it communicated “volatile and subject to change” a lot more clearly than things like “head of main” etc

Thank you. Videos about comparing Linux distros for gaming are clickbait at best, but are ususally an admission that the videomaker doesn’t know what they’re talking about at all.

Think about it like this:

• with ansible, you are responsible for making sure that executing the described steps in the described order leads to the desired result

• with nix, you describe what you want your system to look like, and then figuring out how to get there is nix’s problem (or rather, is obvious to nix thanks to nixpkgs)

?

Better open a package request (or pull request :D) then 😄

No but you see those are people

Yeah but they can at least buy their bullshit, i.e. “we help gut overspending and Make America Great Again”. What’s the supposed mission here? “We help you fap to people that don’t want to he fapped to”?