• vertexarray [any]
    ·
    4 years ago

    It looks like you can just do ./db-init.sh in a terminal in the server directory

    • bottech [he/him]
      ·
      4 years ago

      FATAL: Peer authentication failed for user "postgres"

      Also there wasnt server directory, that file was in scripts

      • vertexarray [any]
        ·
        4 years ago

        Hmm, I didn't encounter that on my end. I'm not on Linux so it might be an OS difference.

        • bottech [he/him]
          ·
          4 years ago

          Actually these problems might be because i cloned the repository provided in documentation you sent me and not the hexbear backend, i will try these steps with it and see if it works

        • bottech [he/him]
          ·
          4 years ago

          Which backend should i use?

          https://git.chapo.chat/hexbear-collective/hexbear or

          https://git.chapo.chat/hexbear-collective/lemmy-hexbear

          • vertexarray [any]
            ·
            4 years ago

            https://git.chapo.chat/hexbear-collective/lemmy-hexbear is the rust backend, it's the one currently in production. Should use that. Also it has the frontend as a submodule.

            • bottech [he/him]
              ·
              4 years ago

              I managed to execute ./db-init.sh and now that i run cargo run i get

              could not connect to server: Connection refused

              Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?

              • vertexarray [any]
                ·
                4 years ago

                hmm, maybe try restarting postgres? If you could run db-init using its default config, it should at least be on the right port already

                • bottech [he/him]
                  ·
                  4 years ago

                  if by restarting you meant sudo service postgresql restart then it didnt work

                    • bottech [he/him]
                      ·
                      4 years ago

                      i figured how to fix that bug but now i have

                      Specified path is not a directory: "../ui/dist/documentation"

                      • vertexarray [any]
                        ·
                        4 years ago

                        I ran into that one. I think I just had to do a release build of the ui.

                          • vertexarray [any]
                            ·
                            4 years ago

                            if you've pulled the submodules, you'll have the ui folder. do yarn build in there

                            • bottech [he/him]
                              ·
                              4 years ago

                              I havent, ui is empty, should i just pull the frontend into ui?

                            • bottech [he/him]
                              ·
                              4 years ago

                              So, after i cloned frontend into ui and did yarn build there, there are still those errors