This seems majorly flawed. If lemmy.world went down we would then loose a lot information/posts.

Shouldn’t there be a timeout period of some sort, or a way to open a new community of the same name on another instance? Maybe even a backup instance? So say for example

A community on lemmy.ml is created. Let’s call it awesome-community. The moderators of awesome-community set backup of awesome-community to lemmy.world awesome-community. Then all instances on fediverse will see that information and if a user tries to view awesome-community lemmy.ml and it says offline then it redirects to awesome-community on lemmy.world.

I think having redirects for offline communities would be great. Even if you could set a timeout feature so say after 24hrs offline redirect. If not been 24hrs then just show it’s offline.

I would documented everything as I go.

I am a hobbyist running a proxmox server with a docker host for media server, a plex host, a nas host, and home assistant host.

I feel if It were to break It would take me a long time to rebuild.

I ran into these issues with sonarr. I believe my fix was how the volumes were labelled. My understanding is they communicated the directory but if the other sonarr doesn’t know where to look for it, it won’t be able to find it

Torrent client - data/downloads:/var/data/downloads

Sonarr - data: var/data

This was when the torrent client is passing the location to sonarr is says thesimpsons.mp3 is located in data/download/the Simpson.mp3 and sonarr can then locate it