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:
- 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
What I meant is that overloading the CPU on a Raspberry running pi-hole will make the whole network misbehave and timeout, until DNS requests are able to be serviced again. But since they're not doing that it should be fine :)
It's there any way around this? I don't want my smart home applications to run sluggish. They need to have priority.
I would say not in a way that makes sense, there may be hacky workarounds like setting
nicepriorities or messing around with scheduling, but there's no way around hardware limitations. The Pi's CPU, RAM, and IO bandwidth are what they are, and you need overhead to guarantee "snappiness"This is what the nice command is for
Scheduling priority on Linux is borderline broken. Nice doesn't even do anything noticeable on modern systems.