Justin

I have a grandfathered purchase of their app on android, works very well

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.

Super reasonable. We had a 2004 Honda Pilot at the time, which still had a tape deck.

I swear, even ebikes are starting to get all these GPS tracking features 😅 such a dystopia.

We were using this well into 2010 or so. Better audio quality than an FM tuner as long as the electromagnet wasn’t overheating.

The best option though was to get an inline FM injector and plug it in where the antenna plugged in. Perfect audio.

Fellas is it gay to have healthy thoughts about your own self worth?

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.

not to mention there are 48 and 64gb dimms out now too that work with basically all alder lake atoms

Yeah, what you’re talking about is called GitOps. Using git as the single source of truth for your infrastructure. I have this set up for my home servers.

https://codeberg.org/jlh/h5b

nodes has NixOS configuration for my 5 kubernetes servers and a script that builds a flash drive for each of them to use as a boot drive (same setup for porygonz, but that’s my dedicated DHCP/DNS/NTP mini server)

mikrotik has a dump of my Mikrotik router config and a script that deploys the config from the git repo.

applications has all my kubernetes config: containers, proxies, load balancers, config files, certificate renewal, databases, clustered raid, etc. It’s all super automated. A pretty typical “operator” container to run in Kubernetes is ArgoCD, which watches a git repo and automatically deploys any changes or desyncs back to the Kubernetes API so it’s always in sync with git. I don’t use any GUI or console commands to deploy or update a container, I just edit git and commit.

The kubernetes cluster runs about 400 containers, most of them just automatic replicas of services for high-availability. Of course there’s always some manual setup steps outside of git, like partitioning drives, joining the nodes to the cluster, writing hardware-specific config, and bootstrapping Argocd to watch git. But overall, my house could burn down tomorrow and I would have everything I need to redeploy using this git repo, the secrets git repo, and my backups of my databases and container /data dirs.

I think Portainer supports doing GitOps on Docker compose? Never used it.

https://docs.portainer.io/user/docker/stacks/add

Argocd is really the gold standard for GitOps though. I highly recommend trying out k3s on a server and running ArgoCD on it, it’s super easy to use.

https://argo-cd.readthedocs.io/en/stable/getting_started/

Kubernetes is definitely different than Docker Compose, and tutorials are usually written for Docker compose.yml, not Kubernetes Deployments, but It’s super powerful and automated. Very hard to crash once you have it running. I don’t think it’s as scary as a lot of people think, and you definitely don’t need more than one server to run it.

nah you’re probably not going to get any benefits from it. The best way to make your setup more maintainable is to start putting your compose/kubernetes configuration in git, if you’re not already.

Ah, no, Kopia uses a shared bucket.

Seems like a good way to do it.

Keep in mind Kopia has some weirdness when it comes to transferring repos between filesystem and S3, so you’d probably want to only keep one repo.
https://kopia.discourse.group/t/exported-s3-storage-backup/3560

Backblaze B2 is a cheap S3 provider. Hetzner storage box is even cheaper, but it doesn’t support S3 natively, so you’re likely to run into issues with the kopia repo compatibility I mentioned.

PHP does actually scale better than something like Lemmy which is written in rust

But sure, you can act like you know more than the Nextcloud devs

Isn’t Opencloud just extended Nextcloud? (Still PHP)

https://nextcloud.com/blog/opencloud-the-digitally-sovereign-workspace-from-hkn-univention-and-nextcloud/

Also, nextcloud core components are written in Rust, the PHP just handles incoming requests.

https://nextcloud.com/blog/nextcloud-faster-than-ever-introducing-files-high-performance-back-end/

Buy used Samsung pm983s on ebay. Super cheap, super fast, and they have power-loss protection. Only downside is that they’re M.2 22110, not m.2 2280. There’s also a bunch of cheap Samsung and hgst u.2 drives on eBay, but you’ll need an adapter.

The sqlite database that Jellyfin uses tends to get corrupted easily, especially if the disk gets full.

The main big feature that Jellyfin devs are working right now is a complete overhaul of the internal database system:

https://github.com/jellyfin/jellyfin/issues/13047

Kubernetes is more stable than docker compose. Docker compose is fishing for containers after the ship capsized. Frustrating and nothing works out of the box.