Well I wasn’t trying to, exactly. Just trying to convey that RAID5 is not considered reliable and that I was urging the commenter to ensure they have a backup if that’s what they are going to use. Regardless of how you configure your NAS, you can always lose data by mistake.

Please consider RAID6 or ensure your data is fully backed up. RAID5 falls flat if a drive fails during resilvering the array.

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Check the title

It’s all OSS.

I’m using Dynu for DDNS. They support subdomains as part of their DNS. You can configure nginx to service/route requests to each subdomain differently.

I opted for dynamic dns and reverse proxy. I configured my reverse proxy to use TLS and also to require client certificates, which I install on my devices. You get so much flexibility and added consistency to your application security that I feel it is a must.

Make that RAID Z2 my friend. One disk of redundancy is simply not enough. If a disk fails while resilvering, which can and does happen, then your entire array is lost.

Removed by mod

Removed by mod

Consider moving to RAID-6. Single redundancy is not cool anymore.

Removed by mod

I’m struggling with this too, but I think the idea is that it allows for fully synchronous requests. You can wait for something long running to finish or for response data to be returned (this could be a generated AI response) and still close out the initial request. The old way to do it was to issue the service call and then monitor the state of the entity to confirm it changed.

I also think it can help with multiple service calls tied into the same verbal request (e.g. “Turn on the light and open the shades”).