Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I have to agree, RAID has only one purpose - keep your data/ storage operating during a disk failure. Does not matter which RAID level or SW. Thank god you mentioned it before.
There can be benefits in addition depending on RAID level and layout, for example read & write speed or more IOP/s than an individual disk (either SSD or HDD). However, the main purpose is still to eliminate a single disk as a single point of failure!
Back to topic - if you have a strong requirement to run your services which (rely) on the SSD storage, even if a disk fails - then SSD Raid yes.
For example.: I have s server running productive instances of Seafile, Gitea, and some minor services. I use them for business. Therefore those services have to be available, even if one disk fails. I cannot wait to restore a backup, wait for a a replacement disk and tell a client, Hey, sorry my server disk failed” (unprofessional)
For protection against data loss - backups: one local on another NAS, one in the cloud. 👌🏼