Trans
Just a individual living life and enjoying it, love life whilst it lasts
I’m pretty sure -r flag actually stands for –resizefs. When you include it, lvextend automatically runs the appropriate resize command (resize2fs) for you in the background immediately after the volume is expanded.
Which makes it a convenient, single-step process.
Do a backup image of the partition first before you run these commands.
If you decide to use all free space: sudo lvextend -r -l +100%FREE /dev/ubuntu-vg/ubuntu-lv
Should suffice I’m pretty sure.
Reddit moment: criticizing Reddit under a Reddit ad.
Yeah, autocorrect got me on my phone — fixed now 👍
If you point Traefik’s forwardAuth at the internal service (e.g. http://<tinyauth-ip>:3000/api/auth/traefik), TinyAuth doesn’t see the correct X-Forwarded-* headers or original host, so it won’t return the auth headers properly.
if you switch to using the public URL instead, the headers should start working — but only once using the full endpoint:
https://tinyauth.domain.tld/api/auth/traefik
Not just the root URL.
That way:
Also worth double-checking that your header names match exactly (e.g. Remote-Groups vs Remote-Group).
So in short: don’t call TinyAuth directly by IP, go through the domain + correct path.
I run a modest Lemmy instance (lemmy.blehiscool.com). It’s not on the scale of lemmy.world or anything, but it’s been around long enough that I’ve had to deal with some real growth and scaling issues. I’ll try to focus on what actually matters in practice rather than theory.
I’m running everything via Docker Compose on a single VPS (22GB RAM, 8 vCPU). That includes Postgres, Pictrs, and the Lemmy services.
This setup is great right up until it suddenly isn’t.
The main scaling issue I hit was federation backlog. At one point, the queue started piling up badly, and the fix was increasing federation worker threads (I’m currently at 128).
If you run into this, check your lemmy_federate logs—if you see:
“Waiting for X workers”
that’s your early warning sign.
Once your infrastructure is stable, the technical side becomes pretty low-effort.
The real time sink is moderation and community management. Easily 90% of the work.
On the technical side, my setup is pretty straightforward:
pg_dump + VPS-level backupsBackups are boring right up until they aren’t. Test your restores. Seriously.
The main gaps I’ve run into:
Pictrs storage growth Images from federated content add up fast. Keep an eye on disk usage.
Postgres tuning As tables grow, default configs start to fall behind.
Federation queue visibility There’s no great built-in “at a glance” view—you end up relying on logs.
Nothing fancy, just consistent habits:
Daily (quick check):
Weekly:
Monthly:
As needed:
If I were starting over:
Happy to answer specifics if you’re planning a setup—there’s a lot of small gotchas that only show up once you’ve been running things for a while.
Me too.
Yeah, a lot of us migrated over. It feels a bit weird at first but you’ll get the hang of it pretty quickly. Just have a look at the communities you can join that interest you!
Welcome!👍