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
Exactly what I was wishing for. Or Rust. Don't care. At least something that doesn't eat resources for breakfast.
I actually contemplated starting such a thing. But before I dive into another project I likely don't finish, I was hoping for something out-of-the-box.
Wasn't this reported as a bug on their repo? Does anyone know why is it eating such an amount of ram? It might be that this can be fixed.
I think all the RAM related issues were closed a while back and were supposedly fixed. I just don't understand why when interfacing with the front-end, it uses so much it would get OOM kill itself with 1.5 GB allocated memory.
Every page, as well as loading in the initial dashboard from an idle state, spikes the RAM. Are there no clever lazyloading happening or something? Surely viewing and modifying database entries can't be this memory intensive?
Maybe it's just an unoptimized Python thing. I stopped self-hosting stuff written in Python, with the exception of Linkding (which takes a while to also submit a link) and Whoogle.