Hello sh.itjust.works community,

It’s been a while since my last update, and I owe you all a more detailed one soon. However, today I’m here to give you a heads-up about the upcoming upgrade.

Over the next 7 days, I’ll be upgrading the instance to v19.5. While this update doesn’t strictly require it, I’ve decided to take this opportunity to upgrade our Postgres database from version 15 to 16 as well. This process can be time-consuming and have take up to 2 hours to complete on other instance.

I’m optimistic that we’ll complete it in less time, but to err on the side of caution, I’ve scheduled the maintenance window for 120 minutes.

To minimize downtime, I’ve split the upgrade into two phases: Phase one will cover the database update, and Phase two will handle the Lemmy code upgrade.

Note: If the database upgrade is completed in under 60 minutes, I’ll proceed with the Lemmy code upgrade during the same maintenance window.

Here’s the tentative timeline:

Task Date Expected Downtime
Upgrade of Postgres Database Friday September 20 2024 @ 8:00PM ET 60-120 Minutes
Upgrade to V19.5 Monday or Tuesday September 23 or 24 @ 8:00PM ET Up to 30 Minutes

During these two planned events those who want to provide moral support or who want to get periodic updates are more than welcome to join us on our matrix channel

edit: 9:23EDT - Hey all, the database and lemmy codebase has been upgraded to v19.5. The database upgrade took a lot less time than expected so I went right into upgrading the codebase. A whole bunch of background tasks are still running which might make your experience slower than usual. Things should be back to normal in the next couple of hours.

  • Draconic NEO@sh.itjust.works
    1·
    2 months ago

    If the instance updated how come it still says 0.19.3 in the web client?

    Cleared cookies and it’s now showing the updated version number and version features.

  • Quacksalber@sh.itjust.works
    0·
    2 months ago

    I no longer see separated up- and downvotes for comments and neither an option to change that in the settings, despite the changelogs mentioning it. Any ideo what’s up with that?

    • TheDude@sh.itjust.worksOPMEnglish
      1·
      2 months ago

      This is odd. I did not upgrade pictrs (the service responsible for image hosting). There may have been an error for some specific tables rows during the database migrates. Another possibility could have been an error during the schema update that I believe the new version had to go through.

      Would you be able to DM me links to other posts that you come across with broken images? I will look to see if I can identify any common trends that could tell us more.

      Thank you

      • threelonmusketeers@sh.itjust.worksEnglish
        1·
        2 months ago

        Would you be able to DM me links to other posts that you come across with broken images?

        I can’t find any at the moment, and my original example seems to have resolved itself. If I come across any others, I’ll send them your way.

  • threelonmusketeers@sh.itjust.worksEnglish
    0·
    2 months ago

    Awesome! Thanks, Dude! Keep us posted!

    Do let us know when we can donate as well. While I appreciate your continued generosity, I would feel more confident in the long-term future of the server if the financial costs were decentralized a bit. It would be nice to know that the future costs are covered for the next x months/years.