443

[Done] New try at upgrading to 0.18.1 July 1st 20:00 CET (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world

274 comments fedilink hide all child comments

We'll give the upgrade new try tomorrow. I've had some good input from admins of other instances, which are also gonna help troubleshoot during/after the upgrade.

Also there are newer RC versions with fixed issues.

Be aware that might we need to rollback again, posts posted between the upgrade and the rollback will be lost.

We see a huge rise in new user signups (duh.. it's July 1st) which also stresses the server. Let's hope the improvements in 0.18.1 will also help with that.

you are viewing a single comment's thread
view the rest of the comments

[-] Jordynl@lemmy.world 7 points 1 year ago

Can't you disable the post button within the upgrade progress? It's a shame to see posts to disappear due to it.

[-] innermeerkat@lemmy.world 0 points 1 year ago

The best would be to redirect to a 502 for the duration of the migration. Better safe than sorry

[-] Mereo@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

I think a static page page explaining to users that the server is being upgraded would be best.

[-] BitOneZero@lemmy.world 2 points 1 year ago

I think a static page page explaining to users that the server is being upgraded would be best.

Beehaw.org did this, their nginx seems configured to return a nice error message.

[-] innermeerkat@lemmy.world 1 points 1 year ago

Exactly. That's what I meant by a 502. Like most HTTP responses, you can associate a template with it and it's even recommended when you have a lot of people using your service and you want to explain why it's not accessible right now.