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:
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?
Besides RAM, what resources do you think you're saving? Not CPU cycles or IO ops, because you're processing the same amount of DB queries either way. Not power consumption, since that isn't affected by RAM utilization. Maybe disc space? But that's even cheaper than RAM.
You're mischaracterizing what I said. My point is that running multiple DB processes on a server isn't going to have a significant impact on system load, if all other factor are kept constant.