In my opinion in modern computing I'd rather be on a "faster" releasing distro such as Fedora, Arch Linux. Modern hardware depends constant patches to the kernel to keep up with new sleep management changes and improvements to the GPU stack etc.
anthr76
joined 2 years ago
I am :) you still need a PVC for the db though. Granted I plan on now moving that to nvme block storage.
I think it’ll be okay if Brooklyn ceases to exist :P
-Knicks fan
Firstly, awesome to hear you're using bjw-s app-template helm chart. He's my good friend and former coworker :)
I'm also doing what @seang96@exploding-heads.com is doing.
While I don't consider this completed yet I have posted how I'm doing things so far here
RIP Knicks dreams 😭
With valetudo you should be able to accomplish what you're looking for. They also have a list of supported vacuums my friend owns the Dreamtech Z10 and highly recommends it. I'm waiting for my current Wyze hand me down to kick the can then I plan on picking it up :)
+1 to Trillium. I looked long and hard on this before settling on obsidian with the livesync plugin.
My personal gotcha with Trillium was that it required sqlite over something like postgres and that web based editors was less important to me.
I'm more of a Kubernetes the Hard way kind of person, but I think it can be suitable for certain production workloads. I'd trust a production workload on it way more then Docker Swarm
I agree with this. I think single node or not the industry is moving towards Kubernetes for container orchestration. Docker has showed their evil intentions and it’s time to leave them in the past. Even podman has native kubernetes manifest support (albeit limited last i checked) as @rs5th@lemmy.scottlabs.io pointed out there’s good avenues to take if you want to avoid the complexities of kubernetes like k3s.
This would be almost too good to be true. I would to happily help fund.
Maybe I'm blind but I don't see the sorting options you mention.