Yeah that’s true, in the case of just running a premade compose file sqlite is the better choice for sure

Oh lol I see, it happens

Performance isn’t the only advantage to a full postgres deployment. I have a central database for all of my self hosted apps which makes it really easy to back it all up.

I’ve had a lot of problems in the past from software crashes that left sqlite files in a corrupt state, backups where the sqlite file wasn’t properly closed leaving it in a weird unlockable state, transactions not completing when swap is used, etc. Besides that sqlite really doesn’t play nice with NFS, which is the basis for quite a few cloud storage providers.

“Best option” really depends on what self hosting looks like in your specific setup.

Why would you need this for your scenario? If you’re not downloading you can simply check the listenbrainz recommendations in the playlists that it creates for you

I initially generated the talos config with the template script, but using talhelper directly offers a bit more flexibility. The first four nodes in this list are the cm4’s

https://github.com/SquaredPotato/home-ops/blob/main/talos%2Ftalconfig.yaml

I also wrote down my setup steps, check here:

https://wiki.abchost.nl/s/cm4-talos-setup

Depending on what you’re going to do with the cluster, 4gb of RAM per node feels rather limiting.

Anyways, as far as storage goes I’m using 4 compute blades loaded with 4 8gb RAM versions of the CM4, each with a 500gb Samsung PM9A1 running Talos to save a bit on that precious RAM.

Got Talos up and running with some help from Onedr0p’s cluster template which saved me a lot of time on the learning curve.