today’s (later than planned) upgrade to lemmy 0.19.2 provisionally appears to have gone alright. if you see excessive amounts of jank (and your page footer can’t decide what version of lemmy it’s running on, IE it shows separate FE and BE versions), clear your browser cache and cookies since lemmy doesn’t seem to do that cleanly on its own

next up I’m planning to deploy the Proton frontend as an alternative to the default and I’m also going to start pushing code to codeberg (most likely) so stay tuned for that

  • self@awful.systemsOPMEnglish
    3·
    10 months ago

    By the way, clean upgrades are completely possible if you know what you’re doing.

    oh do tell

      • self@awful.systemsOPMEnglish
        3·
        10 months ago

        no thx but while we’re here

        the reason why the cache busting broke is because I’m building for an immutable environment (NixOS sans docker) and my builds don’t have .git cause it’s a source of mutability. lemmy’s cache busting utterly breaks without git but it still incorrectly marks the files as immutable, breaking a ton of users. utterly broken behavior.

        but the very funny part is the cache behavior isn’t even the bug that’s breaking everything right now. that’s this bug: https://github.com/LemmyNet/lemmy-ui/issues/2325 which you didn’t mention as a factor while you were trying your best to sound smart

        also, have you ever gotten banned from an instance for being a shithead reply guy before? I’m betting this ain’t the first time

        • self@awful.systemsOPMEnglish
          4·
          10 months ago

          I frequently roll out new upgrades on lemm.ee without any downtime (so some servers running 0.19.1, some running 0.19.2 for example).

          also motherfucker, those versions are compatible! no shit there’s no downtime for a hotfix upgrade. we got into this mess upgrading from 0.18.4 to 0.19.2 cause nobody seemed to think the upgrade process through in any detail

          for anyone interested, the hack that NixOS uses to fix the asset path is here. the config we’re running predates that, and we may not be able to use that hack with a flakeified lemmy-ui (which is what makes it a hack — using src.rev like that is brittle and feels like it breaks Nix’s abstractions. maybe using git hashes like this is actually a bad fucking idea, huh? and the real fucked up part is, the UI knows its version so they could use that, but they woke up and chose jank)

        • sunaurusAEnglish
          1·
          10 months ago

          Btw, you can for sure make cache busting work even with your non-supported setup. I am not using a standard setup for lemm.ee either.

          Feel free to ping me on Matrix if you decide you want to fix this, and I can help you out. Not sure you want help at this point, though, if you were just venting, then carry on.