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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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 run an instance just for myself and it was a nightmare on HDD and 16 GB RAM. It was slow as molasses. Supposedly the database layout will be fixed with the 1.0 release that is just around the corner.
Since I upgraded to 64 GB it's been pretty smooth. Still wild that that is necessary for a single user.
Also, disable image proxying. I have no idea what pict-rs does but it seems to be too much.
You should consider running Piefed instead. It's not as resource hungry as Lemmy.
Question, what is the purpose of running an instance for yourself ?
Control. I'm not beholden to anyone. My server is federating exactly those communities that interest me.
No I get that, but what do you do on it??
Same stuff you do on any other instance. Looking at stuff, upvoting, downvoting, posting and commenting.
Ohh I see now. I was just wondering why you'd make a community for only yourself so I didnt get that. But you'd basically have it for your account to live on.
Hey, this is really useful.
I wanted to ask a few follow-ups, because the jump from 16 GB to 64 GB sounds pretty dramatic:
I’m trying to separate “Lemmy really needs big hardware” from “a specific part of the stack was the real problem”.
Sorry if some of these questions are a bit basic or oddly specific — I’m using AI to help gather as much real-world Lemmy hosting experience as possible, and it generated most of these follow-up questions for me.
I was and still am on HDD. The CPU was upgraded as well. I migrated to a new server.
The main culprit was the database. As far as I'm aware Lemmy is missing some indexes and due to the ORM they used didn't always have optimised queries. Now with 64 GB RAM the whole database (almost 30 GB) fits in there fixing most of those issues.
The real fix will probably come with Lemmy 1.0. They radically changed the database layout and queries.
Image proxying wasn't bad for performance. Just storage space. It was growing really really fast. Now that only I am using it to host the pictures I uploaded it is still much too large (24 GB). But its directory structure is so convoluted that I can't really debug it. My stuff really shouldn't be taking up more than a few hundred MBs.
I am the only one using this instance. I am subscribed to a hundred communities or so. I am always pretty up to date with my Lemmy versions.
Do you mean a 64GB SSD or did you really have to upgrade to 64GB RAM to run your Lemmy instance?
RAM. Maybe 32 would have been enough but 64 cost as much as 32 so that decision was easy.