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
I think it depends heavily on how much storage you're allocating, if you allow uploading media that is. From what I've understood most of the bottlenecks are in DB operations so CPU and memory definately play a role.
Good point. I forgot about media.
I wonder if I made a LAN lemmy instance if I could use it as a lemmy cache server.
Is there a such thing as a cache only server? If so I'd love to sign up as being a cache bitch and help out!
I've not looked to see if it's possible, but a lemmy instance with posting disabled would be effectively be a cache server - all reads, no writes, except for sign ups, I think.
I was thinking if I made a personal instance I could use it as a local "cache".