Im looking at setting up a lemmy instance on a rpi3 with cloudflared tunnel! I'm curious to see if anyone else has done this and how it was.
Edit: I'll give it a whirl and hopefully post an update from my new instance later!
Im looking at setting up a lemmy instance on a rpi3 with cloudflared tunnel! I'm curious to see if anyone else has done this and how it was.
Edit: I'll give it a whirl and hopefully post an update from my new instance later!
Please don't forget to give us updates on your adventure^^
I was able to get it setup, main things to watch out for:
I only used it for testing purposes, but performance was fine (on a Pi4 4gb). Note I only ever had one user.
As I only want to use it for myself as jump-off point (and to mess around a tad) I'm fine with performance on an RPi4 (have the 8 GB version), but I'm struggling to get it next to the rest in my Debian install on it.
Local install fails as I need imagemagick 7 (Debian still had 6.9), and it refuses to compile with imei method. (that script wants to use /usr/local/bin/identify which I think it needs to install itself (part of imagemagick) and the compose file I couldn't get to work with an external (already hosted) postgres.
Any tips? I'm totally new with docker and ansible.
What user cap would a pi have running an instance?
Are you asking me what i plan to set the cap to? I guess just me. I cant see anyone else wanting to run off a pi from my house and there are so many other instances to join.
No, I meant what is the user limit based on the power of the raspberry pi tech specs.
Basically the limit would be the speed of the database and the drive it runs on. If you connect a SATA SSD via usb3 it shouldn't be too bad. Can't tell you exact figures but a few hundred users is probably ok if you don't expect the site to be super responsive.
Thanks. Might be useful for there to be a table outling diffrent hardware configs and acceptable user loads as more people people consider creating instances.
its difficult because different users have different usage patterns.
for example, two users who never post and are never online at the same time really take no resources from each other. they are effectively "one" user.
one user who posts 10gb of content a day, and is constantly posting would be equivalent to hundreds of "normal" users.
Yes, sure, didn't want to complicate the question by adding that :)
I’m a newbie here but what would be the benefit of running an instance just for yourself?
The ability to host your own data - both for privacy, and insurance that the instance you host your account in won’t suddenly disappear.
I would also add that Lemmy is part of the fediverse, meaning it is federated. Federation means all instances "talk" to all instances (unless they defederate), so you aren't limited only to the content on one instance (or in some cases not even Lemmy, case in point: I'm posting this from my kbin.social account).
Hey OP, I'm on a similar journey (except I'm using an rpi kubernetes cluster)
I don't have advice but I do want to wish you good luck
Here: my daily "simply a nice stranger" award goes to you
Not yet, but I'm planning to. And I don't think there will be any "pitfalls" at all other than your microsd dying in a couple of months rather than years due to it getting hammered constantly by API requests, etc.
You could plug in a USB SSD or HDD and make sure the DB and other regularly written data goes there. That would pretty much remove the problem.
I would wonder how well it would perform. The limited memory and cpu power surely would make database access not great under even moderate load.
You are right -- I completely forgot about those, thanks.
I would wonder how well it would perform.
Something between "usable" to "a complete nightmare" -- depending of how popular the lemmy instance is. Which would scare new users away, leaving it as a "cool kids only" thing. Then again, theres the fact that the power draw is little to none, which is very important regarding most self-hosting stuff -- "can't use it if I can't maintain it".
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!