I recently self-hosted Voyager and it was a very painless process, I’m very pleased!

I noticed some strange behavior: When I navigate to my Voyager instance from Chrome, everything works as expected. When I install the PWA from Chrome, the list of Lemmy instances doesn’t match my CUSTOM_LEMMY_SERVERS variable; it’s the same list as vger.app. Then, if I navigate from Chrome to my Voyager instance, the list is now also the same as vger.app. None of this happens if I install the PWA from Firefox (it seems that Firefox installs PWAs differently from Chrome though; it doesn’t show up on the app drawer, for example).

I suspect the PWA doesn’t actually come from my server when I install it from Chrome. Is this what’s happening? Or am I doing something wrong?

EDIT: this issue is now fixed, build the Docker image from the source code to try it out. Thank you @[email protected]!

    • gnzl@nc.gnzl.clOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      It is indeed a cache issue. When I clear the cache I can start over - go to my Voyager instance, see the custom Lemmy servers I defined, and install the PWA. When I load the PWA though, my list of Lemmy servers changes to the same list you see on vger.app. My suspicion is, then, that Chrome doesn’t install the PWA from my server (maybe from vger.app?), and that installing the PWA “overwrites” my Voyager instance and I see this overwritten version from that moment on.