Wow! There's some really cool stuff coming up. https://mlmym.org/lemmy.kutara.io/ is very impressive :)
anthr76
While I agree I think the answer changes weekly :)
I use ceph block storage
I had a toppin jersey. I believed in his potential. I hope he gets some minutes now. I think he worth more then two second picks.
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 @[email protected] is doing.
While I don't consider this completed yet I have posted how I'm doing things so far
RIP Knicks dreams 😭
+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 @[email protected] pointed out there’s good avenues to take if you want to avoid the complexities of kubernetes like k3s.
Purity face wash