Lemmy and Lemmy-ui are pretty much stateless and thus horizontally scalable. Pictrs and Postgres take a bit more work.
I'm not a dev though. Just my own experience hosting my own instance.
Lemmy and Lemmy-ui are pretty much stateless and thus horizontally scalable. Pictrs and Postgres take a bit more work.
I'm not a dev though. Just my own experience hosting my own instance.
Happens here too. Odd
Your post will be stored on both instances. Any media like pictures or videos will only be stored on your instance. Media will be referenced if the content is being viewed on another instance. At least I think so.
midwest.social/c/projectzomboid is showing up on my instance.
The domain midwestern.social does not exist in public DNS. See https://intodns.com/midwestern.social That might be a temporary issue, but without resolution nothing else is going to work.
What's the url? Does it show up locally for you?
Shows up where? If you mean locally, it should be instant.
Or run their own instances. More instances would really help spread the load.
It lasts until the issue is resolved. It typically means Lemmy is not responding in time, and the web server is returning the 502 error after it timeouts.
Are posts stored the same way?
I've learned something new :)
Can you tell me why my comments show up at lemmy.ml even if my instance is turned off? Is it a cache thing, or is the content copied / stored at lemmy.ml?
I've tested running multiple instances of pict-rs using distributed storage (Moosefs) for the uploaded file directory. I ran into several weird issues. Mainly that images would not load, or end up broken. But then refresh the page and hit a different pict-rs instance and it worked for some images, but broke for others. So now I run a single pict-rs instance, still on distributed storage, but everything works. This is on the 3x branch. I believe the 4x branch is still in rc stage.