this post was submitted on 24 Jun 2023
41 points (100.0% liked)

/0

2021 readers
1 users here now

Meta community. Discuss about this lemmy instance or lemmy in general.

Service Uptime view

founded 2 years ago
MODERATORS
db0
41
Upgrading to 0.18.0 (lemmy.dbzer0.com)
submitted 2 years ago by db0 to c/div0
 

I'm am looking to upgrading versions soon. Unfortunately there were massive changes in the reverse proxy setup, which means I need to change a lot of things in my reverse proxy setup. I am hoping I don't cause too much of a downtime, but if I know, you now know why

top 8 comments
sorted by: hot top controversial new old
[–] RandomLegend 2 points 2 years ago (2 children)

Do you think it would make sense to host something like uptime-kuma for that instance? That way we could see if your server is down or if it's again some shenanigans with the frontend apps on mobile lmao

[–] [email protected] 2 points 2 years ago (2 children)

Honestly, given that probably all fediverse instances are in the same boat, I wonder if it'd make sense to have some kind of centralized mechanism for registering a server and indicating whether there's planned maintenance or that the thing has permanently gone down, or whatever.

Also, even other instances and clients might want that information available to them, so that they can help inform the user as to instance status in their UIs.

[–] RandomLegend 2 points 2 years ago

Yeah that would absolutely make sense, but centralizing it for all the Lemmy's will be impossible

[–] db0 1 points 2 years ago

The fediseer could do something like that, where admins could mark their servers as maintenance, or "under raid" etc

[–] db0 1 points 2 years ago

If you tell me how to set it up, sure

[–] Stanley_Pain 2 points 2 years ago
[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (1 children)

I didn't change my Caddy reverse proxy at all for my upgrade, did they change the API routes? Or was it just Nginx changes?

[–] db0 2 points 2 years ago

yes, they changed a lot of the routes. There's no an internal nginx in the docker and a lot of the external nginx is just sending to one port.

load more comments
view more: next ›