Legend, thank you!
Legend, thank you!
Since you mentioned MLC, maybe you have some suggestions for eg used server grade disks? Would the Rpi be able to run something like the Intel datacenter SSDs eg S3700? The power loss protection is really something I would like to have, especially in a homelab scenario. Or any other notable MLCs with larger capacities? I am having trouble finding a good list sorted by max potential storage.
Crucial is fine but IIRC the 1TB+ variants are too good to be true (cheap) and will die quite fast. Just a note for everyone to look into the underlying technology on the particular model.
Log2ram is a service which keeps your log files in RAM, avoids the constant writes to disk and really helps with SDcard longevity. Probably helps with SSDs too.
You can just Google it and check out the github page, no need for LLM accuracy lottery
I do not have to share passwords with 10-50 people and neither did the op imply this. I am having trouble figuring out the reasoning behind your message. Why would this be a normal use case?
I mean this comment well. You seem to be clueless about the problems open source projects are facing. Free work and hopefully the maintainer doesn’t burn out before he can hand the torch to another person.
Are you not aware of the countless issues with absolutely unsustainable open source projects out there in the wild?
We need a cultural change and a way to normalize supporting and paying (whoever can afford to) for good open source projects.
I am importing my externally synced and managed library to immich. It does not create any structure or edit the files.
Yes, a thousand times this. DeSEC is awesome, I moved my domain record management there. I’m usually buying domains on namecheap, and the IP allow list thing for the API was just too annoying to deal with.
Mine was off, just checked.
The last time I had to send 30 Euro to someone, I had to pay 5 Euro for gas fees. It used to be even worse. Your statements are bullshit, we all know what the usual use cases are (other than speculation)
This, letsencrypt with dns challenge, https://desec.io/ to manage the dns records https://github.com/go-acme/lego or traefik to manage the certificates and do the dns challenges for you.
Running ZFS on consumer SSDs is absolute no go, you need datacenter-rated ones for power loss protection. Price goes brrrrt €€€€€
I too had an idea for a ssd-only pool, but I scaled it back and only use it for VMs / DBs. Everything else is on spinning rust, 2 disks in mirror with regular snapshots and off-site backup.
Now if you don’t care about your data, you can just spin up whatever you want in a 120€ 2TB ssd. And then cry once it starts failing under average load.
Edit: having no power loss protection with ZFS has an enormous (negative) impact on performance and tanks your IOPS.
This, just pgdump properly and test the restore against a different container. Bonus points for spinning as new app instance and checking if it gets along with the restored db.
Cheap panels are tanking European competitors, but it’s probably too late to intervene at this point. Can’t compete with work camps and cheap slave labor.
Symfonium is great, it supports a bunch of sources and works really well. Absolutely worth supporting the dev (check his ko-fi too)!
Oh okay that’s a lot of power. For reference, I just set up an old Haswell PC as a NAS, idling at 25W (can’t get to low Package C states) and usually at 28-30 running light workloads on an SSD pool. My plan was to add a 5 disk cage and at least 3 HDDs, with Raidz2 and 5 disks being the mid term goal. Absolutely unnecessary and a huge waste. I settled on less but larger disks, and in mirror I can get 12-18 TB usable space for under 500€. Less noise and power draw too.
Look for 5W idle consumption boards + CPU combos which go down to package C6+ state. HardwareLuxx has a spreadsheet with various builds focusing on low power. Sell half your disks, go mirror or Raidz1. Invest the difference in off-site vps and or backup. Storage on any SBC is a big pain and you will hit the sata connector / IO limits very soon.
The small NUC form factors are also fine, but if your problem is power you can go very low with a good approach and the right parts. And you’ll make up for any new investments within the first year.
The problem is, the libraries and SDK used to build the app will have had vulnerabilities for sure. Same for the underlying image (unless scratch / distroless). We run extensive vulnerability scanning in our pipelines, and Go libs occasionally pop up. The Go SDK also had multiple security fixes in the last year.
Does it support the docker compose plugin / v2 API (the ‘docker compose’ plugin and not the old ‘docker-compose’ command)?