Kubernetes makes distributed storage easy.

Basically, all the components get deployed for you, since that's part of what kubernetes is good at.

And then, services/containers can provision storage by requesting storage via making a "claim" and whatever distributed storage providee you have gives it to you.

https://sso.tax/

It's unfortunately common, even though it probably shouldn't be.

They don't have to support it. It's more that the database they are connecting to supports HA, and/or both are using shared storage. So when one container dies, kubernetes restarts another container on another node with the same shared storage attached.

Docker is often configured to automatically restart containers when a container dies, just in case it's a one off bug or something like that, and kubernetes is like a more resilient version of that.

You can do oidc with the proxmox ui itself.

I use oidc with Incus, which is a fork of lxd and a similar software to proxmox, it can run vm's and lxd containers.

Proxmox is also making their own: https://www.proxmox.com/en/products/proxmox-datacenter-manager/overview

source code: https://github.com/proxmox/proxmox-datacenter-manager

Two more that I have found:

https://docs.pegaprox.com/

And: https://github.com/xdkaine/uma-proxmox-wrapper-public

Ah, I see.

A quick search leads me here: https://discourse.nixos.org/t/nix-on-windows/1113/105

which you might have seen before. It is a very long post, but some people mention having achieved what you want.

~~Multiple options:~~

~~Use flake-utils: https://github.com/numtide/flake-utils#example~~

~~Create a helper function: https://ayats.org/blog/no-flake-utils (what I do)~~

~~flake-parts: https://ayats.org/blog/no-flake-utils#option-a-flake-just-for-yourself , https://github.com/hercules-ci/flake-parts~~

~~But this is one of the things I find annoying af about nix flakes. Reproducibility is a spectrum, and I think focusing on "purity" over being able to easily ship it to multiple architectures, or not being able to use the GPU is a step too far on that spectrum for the vast majority of usecases. I can understand why scientific computing or anything that needs absolute precision might want it, but most people only just want the same versions of packages installed in their development environment.~~

EDIT: whoops forget everything I said, you are asking for cross compiliation of a dev env to Windows. Nix doesn't support Windows. It only supports linux. You can't make a nix dev shell that works on windows.

No. Telegram is not end to end encrypted, by default. Their encryption is only in certain versions of the app. And finally, it's a custom protocol that has never been seriously audited.

Signal doesn't claim they don't share, they claim they can't share the private messages, which is true because it's open source and we can see how the encryption works, and we also know that signa's encryption is always on.

Edit: well, I guess is private messages refers only to "secret" chats encrypted by telegrams end to end encryption, and assuming that their custom encryption isn't backdoored then yes, I guess this claim is true.

But telegram chats are not "secret" by default. It must be explicitly enabled per chat.

When people say that linux adds a second life to bad hardware, they don't just mean making 8 gb of ram usable again. They also mean stuff like this, using dying hardware to it's last breath.

Related: https://lorenz.brun.one/dealing-with-bad-ram-on-linux/

You can mark the failing parts of ram as explicitly bad so Linux avoids them, just like with hard drives. Another way to get more lifespan out of this hardware.

I run a single node cluster.

My single node has 256 gb of ram and 24 cores. I do this because, if you want a lot of ram/cores/storage, it is cheaper to get a used "tower server" type device and then upgrade it as you go over time, than it is to buy entirely new devices for every bit of ram you want to add to the cluster.

I like kubernetes because I like configuration as code, gitops, the way it abstracts over components so I can swap components out easily, the way that helm charts are an easier way of orchestrating containers, and a bunch of other things.

Clustering is merely one of many benefits of kubernetes, one that isn't particularly important to me. Although, my opinion on that has changed somewhat recently. Waiting for a reboot is annoying, since I am rebooting the whole thing and I have to wait for each service to go down or come up before the machine reboots properly. But if I was running kubernetes as a virtual machines inside incus with multiple nodes, I could update each node one by one without the whole thing going down. Or, I could snapshot them, allowing me to reboot the host without waiting for kubernetes. But these things are mostly just somewhat nice to have, rather than a core feature I really require.

I recommend taking a look at this page: https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system

This is probably what you want: https://wiki.archlinux.org/title/Dm-crypt/Specialties#Encrypted_system_using_a_detached_LUKS_header

Or this: https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#Plain_dm-crypt

Which describes how to do what you want on Archlinux. You will have to find some of the analogous docs for Guix.

Okay, upon careful reading, it looks like the option you linked might not be what you want. What you might need is to tinker with the initramfs and the bootloader (explanation on archwiki here*) to find the key from the USB.

Guix does have options for the initramfs: https://guix.gnu.org/manual/devel/en/guix.html#Initial-RAM-Disk-1

You may also have to configure kernel parameters via the bootloader: https://guix.gnu.org/manual/devel/en/guix.html#Bootloader-Configuration-1 (but I didn't see an option for kernel parameters in there.

There is also this for setting kernel parameters: https://guix.gnu.org/manual/devel/en/guix.html#System-Control-Service , but I suspect sysctl is too slow and will activate too late for your needs.

*You should probably read this page if you are unfamiliar with Linux boot process. It works the same on Guix, it's just configured differently.

Even used stuff is expensive nowadays.

Anyway, you can buy these used refurbished small form factor business PC's.

These things: https://www.servethehome.com/introducing-project-tinyminimicro-home-lab-revolution/

I was recently at a tech conference and I met a guy who was selling 16 gb ram one's for 30 usd, since they had managed to track them down that cheap in bulk somewhere. What happens is that corporations or govt get rid of them due to warranty expiry, so they need to be offloaded somewhere.

You probably won't be able to find them that cheap but it's definitely more affordable than new stuff. It used to be cheaper but I mostly see 200 usd in my searches.