Justin

I would probably remove python 2 support, it was end of life when the project was started.

I dont think Immich supports turning a normal account into an sso account, though it may be possible with manual database editing.

At a small scale you can take advantage of advanced irrigation, physical pest barriers, advanced fertilization, and even human or AI based individual plant diagnosis and weeding.

Kubernetes is great for single nodes! It definitely is more advanced than docker compose, but it’s actually not hard at all if you read through the documentation. It definitely makes running containers easier in the long run.

Here is my git repo for my big Kubernetes cluster at home: https://codeberg.org/jlh/h5b/src/branch/main/argo/custom_applications

It started out as just a NFS server and a Kubernetes server running on Proxmox in 2021.

I think one important point is that we have nutrition labels mandated by regulation so that consumers can see how much sawdust is in the rice crispie they’re buying.

The logical extreme would be no regulation at all and expecting consumers to scientifically test every rice crispie they buy to determine the amount of calories in it.

It’s not going to make a meaningful difference in your threat model and it will cause a lot of hassle for extra configuration and broken docker images, so I wouldn’t bother.

There is some nice tooling for transparent user name spaces coming down the pipeline in Kubernetes which will be a nice 0-effort security upgrade, but if you don’t have the tooling, I would say it’s not worth it.

https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces/

Hetzner Storage box is $20/month for 10tb.

Probably not that hard to build a simple flask frontend around it.

Automatically processing files in an S3/WebDAV directory would also be useful.

https://docs.k3s.io/installation/uninstall

There is also a k3s option for Nixos, which removes the security and side-affect risks of running a random bash script installer.

Very true. Each brick you lay upgrades your setup and your skillset. There are very few mistakes in Kubernetes as long as you make sure your state is backed up.

For question 1: You can have multiple resource objects in a single file, each resource object just needs to be separated by ---. The small resource definitions help keep things organized when you’re working with dozens of precisely configured services. It’s a lot more readable than the other solutions out there.

For question 2, unfortunately Docker Compose is much more common than Kubernetes. There are definitely some apps that provide kubernetes documentation, especially Kubernetes operators and enterprise stuff, but Docker-Compose definitely has bigger market share for self-hosted apps. You’ll have to get experienced with turning a docker compose example into deployment+service+pvc.

Kubernetes does take a lot of the headaches out of managing self-hosted clusters though. The self-healing, smart networking, and batteries-included operators for reverse-proxy/database/ACME all save so much hassle and maintenance. Definitely Install ingress-nginx, cert-manager, ArgoCD, and CNPG (in order of difficulty).

Try to write yaml resources yourself instead of fiddling with Helm values.yaml. Usually the developer experience is MUCH nicer.

Feel free to take inspiration/copy from my 500+ container cluster: https://codeberg.org/jlh/h5b/src/branch/main/argo

In my repo, custom_applications are directories with hand-written/copy-pasted yaml files auto-synced via ArgoCD Operator, while external_applications are helm installations, managed via ArgoCD Operator Applications.

helm charts are awful, i didn’t really like cdk8s either tbh. I think the future “package format” might be operators or Crossplane Composite Resources

deleted by creator

all home routers have NAT which functions as a firewall, but VPSes don’t cone with any firewall by default, so you’d have to set one up. Also VPS ranges seem to hotter for scanning.

Yeah, I mean Rust is only verbose if you want it to be. let foo = "bar"; is valid rust too, no need to declare the type and definitely no need to declare the lifetime.

For that matter, if you ever declare something as explicitly 'static in code that isn’t embedded or super optimized, you’re probably doing it wrong.

Your stuff is more likely to get scanned sitting in a VPS with no firewall than behind a firewall on a home network

let a: &'static str

Yeah Stalwart seems to have a lot of momentum, I’ll probably be setting up a server with my kubernetes+ceph cluster this month.

Check out NixOS. It can build qcow images from scratch for you to import into proxmox

https://github.com/nix-community/nixos-generators

I have 8 bare-metal servers and I do everything automated with NixOS, I rarely ever access the servers directly.

Here are the nixos configs for my DHCP server and kubernetes servers that you can use as a base.

https://codeberg.org/jlh/h5b/src/branch/main/porygonz

https://codeberg.org/jlh/h5b/src/branch/main/nodes

For what it’s worth, Ive been using Ansible off and on at work for 8 years, and I think it’s pretty outdated and clunky these days, there are much smarter ways to manage workloads such as kubernetes, cloud-init, terraform, and NixOS. If you don’t want to get into Kubernetes then definitely learn NixOS.

Quick google search points out this blog post for tips and tricks for prototyping stuff like game features in Rust: https://corrode.dev/blog/prototyping/

Definitely something that I’m going to try when I have to time to get back into Rust. Probably good advice for most people who are unhappy with Rust. Being attracted by Rust’s unique optimization tools too early on seems like a big beginner trap.