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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- 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
Zero or one backups depending on the type of data generally.
For a system if it can't be redeployed from a list of requirements then I Foundationally ducked up. It means either I'm depending on something fragile, unknowable or over complicated.
Raw data on the other hand goes on a raid array. If I need more redundancy then that, then a single extra off site backup on a cd or something.
A back up on the same drive as the original isn't a backup. It's a waste of space, and a stupid idea.
A system that requires excessive nonsense is not reliable.
If I have a on and off site back up and both fail. Then either the world is literally fucking on fire and it doesn't matter. Or someone dropped a bomb on my storage.
Either way I have bigger problems at that point.
It's a backup that helps against software errors, but not against drive failures. Depending on what you want to achieve, it's a perfectly valid strategy.
I generally have Operating System backups that are stored on the same drive. Those backups are immediately copied to 3 different devices, my computer and two other drives
The backup on the local drive is useful for when I'm tinkering, making adjustments, adding or removing stuff. Restoring from that local backup is far more convenient than using the remote backups
I don't use anything with a database so all my static media files and wiki's don't go to the local backup. I handle them separately but they are still spread across the 3 other devices in my network