JASN_DE

joined 1 year ago
[–] [email protected] 9 points 11 months ago (5 children)

Always remember: RAID is not a backup.

Having only one backup and the server dying means you now have no backup, therefore the 3-2-1 scheme for backups is worth looking into.

[–] [email protected] 12 points 11 months ago (9 children)

Not sure if it makes things easier than your current setup, but take a look at Mediathekwebview.de

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (2 children)

The official NC docker container uses the "www-data" internally to run the services. This will get important if you ever want to run tasks via "docker compose exec".

 

While it was an interesting and sometimes confusing experience setting up and running my own Lemmy instance (looking at you, 20 character limit on federation URL), I think it's not worth it.

Now the time has come to decommission the service, is there a proper way to do that? I don't mean the local part, that's on docker and gone with 3 lines of bash input. I mean the overall process. How do I tell other instances that mine won't be available any longer? I noticed a constant stream of federation pushes, even with everything deleted and purged. Shutting down the instance won't help either, the requests will simply 404 then, but won't stop, which in itself is only logical. Has anyone done this before and could shed some light on this situation?

Edit: So I played around with the logs some more, there seemed to be an issue with communities that are on "subscription pending". I restored an older database which had all the entries, removed any federation restrictions and tried again from scratch, leaving and joining again until all communities were properly subscribed to.

Then:

  • Unsubscribe
  • Remove
  • Purge

Just to be sure the entries are gone. As of 15 minutes ago, Traefik hasn't logged a single connection to my instance.

Edit2:

Turns out that wasn't it. My instance is on 0.17.4, and even with every community unsubscribed and purged, I'm being hammered by lemmy.world activity_pub events. The formatting is also different, I think that's because they moved to the 0.18 RC stage. So it looks like something somewhere didn't get the unsubscribe announcement.

Edit 3:

So I tried moving to 0.18-RC. Which now means lemmy.world is trying to push the inbox to the frontend? WTH...