• shadow@lemmy.sdf.org
      link
      fedilink
      arrow-up
      9
      ·
      9 months ago

      Yep, and if it becomes a frequent request, add clarification to the readme / wiki / documentation.

      Also, if you push folks towards issues, then they become indexable by search engines! So even if you have a solved problem you can at least find that… Discord? It’s a black hole.

    • JustEnoughDucks@feddit.nl
      link
      fedilink
      arrow-up
      5
      ·
      9 months ago

      And then get it insta-closed withing 20 minutes saying that “this is a problem with your setup, not the software” even when “my setup” was literally setting up their project using their documentation (docker compose files).

      That is how developers treat people with questions that they deem “stupid.”

      It turns out their documentation was wrong and some environment variable that they said was optional, was not actually optional and the service would go into a reboot loop without it. I figured that out no thanks to the devs.

      • crispy_kilt@feddit.de
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        9 months ago

        Update your issue with a pull request fixing the documentation. When you’re doing things on github, 99.999% of your audience is the general public, not the maintainer, because they will find your issue and solution through search engines.