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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Nextcloud asked in a poll at https://mastodon.social/@nextcloud@mastodon.xyz/115095096413238457 what database its users are running. Interestingly one fifth replied they don't know. Should people know better where their data is stored, or is it a good thing everything is running so smoothly people don't need to know what their software stack is built upon?
. >18% of people running next cloud are not backing it up.
This is a fallacious. If you have a very small set of users, what exact data is in the database that you would be upset at losing? Maybe your contacts and your calendar. Which you could back up manually, which might actually be simpler than backing up the database.
I'm sorry, but writing down the data from your organizational program and re-entering it all from scratch is NOT a backup solution.
If you have such scant data to do that, you didn't need to have nextcould installed in the first place.
Where are you getting that from? The fastest and easiest way to back up any server is a full filesystem backup, especially if you're using something like zfs or btrfs.
I can't decide if you don't know what you're talking about or you're just trying to troll me.
Neither, I'm trying to explain that you don't need to know the implementation details of the software running on your server to backup the entire thing.