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!
I don't think there should be any problems, lemmy is a fairly lightweight web application, it's compiled so no big overhead of some runtime like ruby in case of mastodon. I haven't tried it on a raspberry Pi, but on my server the load is always just around 0.1
The only bottleneck I could think of was Postgres, but I've been running postgres on raspberry pies without any problems before too.
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.
So in the official docker-compose.yml lines that define where/how to get the image for that application.
For example:
build:
context: ../
dockerfile: docker/Dockerfile
This tells docker to look for a file called docker/Dockerfile in the parent directory. This means that when you go to call docker compose up -d it will build an image from source using that Dockerfile. For the Pi we don't want this (at least as of 0.17.x; I haven't tested 0.18.0 yet).
Instead we want to use a pre-built image. To do that we need to go to docker hub, specifically: https://hub.docker.com/r/dessalines/lemmy/tags and find the latest tag that matches the architecture of the system we're building on. I assume you're on a Pi4 running a 64bit so, so that gives us 0.17.3-linux-arm64. After you've got that tag we just need to replace those 3 lines above with:
image: dessalines/lemmy:0.17.3-linux-arm64
Now when we go to call docker compose up -d it will pull down that prebuilt image instead of building for source. Btw, you'll want to do the same for the lemmy-ui service.
P.S. I don't have much experience using Ansible, so I can't help here. I normally just SSH directly into the Pi and do everything there.
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^^
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