Permanently Deleted

  • makotech222 [he/him]
    ·
    2 years ago

    I'm working on one of the remaining missing features in upstream lemmy right now, which is Taglines. backend PR is already up on Lemmy git, frontend PR incoming sometime soon. Afterwards, looking to start working on Featured Posts.

  • ella [any]MA
    ·
    2 years ago

    https://hexbear.net/post/159221

    There was a transparency post as well about our progress since then, but it seems to be hidden. I'll reach out to the devs to see if they can get it visible again. There has been no progress since our last transparency post.

  • footfaults [none/use name]
    ·
    2 years ago

    The main issue I have seen is that the Hexbear database data and schema has diverged from upstream Lemmy. There is no direct migration path and one needs to be developed, to transform the Hexbear database and data back to the same schema as upstream Lemmy. Until that happens we cannot run the upstream Lemmy code with the Hexbear data.

    • sexywheat [none/use name]
      ·
      2 years ago

      Hexbear has, for this very reason, inadvertently vindicated my outright refusal to use Minecraft mods and only play vanilla.

      • footfaults [none/use name]
        ·
        2 years ago

        I only had a fixed amount of time that I was able to give to looking at Hexbear and the majority of it was spent fixing bit rot.

        The docker image was not buildable out of the box, the build instructions were incorrect, etc etc.

        By time I got it to the point where I could build and run the code locally, I was out of time.

        https://git.chapo.chat/hexbear-collective/lemmy-hexbear/commits/branch/main/search?q=author%3Afootfaults

        • tagen
          ·
          1 year ago

          deleted by creator

          • footfaults [none/use name]
            ·
            2 years ago

            Everything should build properly and run properly, @layla did some additional bits to finish it off, but if you have problems report them in the Element chat

            • tagen
              ·
              1 year ago

              deleted by creator

              • footfaults [none/use name]
                ·
                2 years ago

                The dockerfile at https://git.chapo.chat/hexbear-collective/lemmy-hexbear/src/branch/main/docker/dev is meant to be for when you compile it and build it locally.

                That's nice that someone has pushed the container images to that registry, so that you could pull them down, but that's not the point of that Dockerfile and docker-compose file.

                • tagen
                  ·
                  1 year ago

                  deleted by creator

                  • footfaults [none/use name]
                    ·
                    2 years ago

                    Yes you also need to build the frontend https://git.chapo.chat/hexbear-collective/hexbear-frontend

                    • tagen
                      ·
                      1 year ago

                      deleted by creator

                      • footfaults [none/use name]
                        ·
                        2 years ago

                        Order doesn't matter, you need to build both hexbear-frontend and lemmy-hexbear to get a local environment.

                        Basically, there's no repository that just contains the docker-compose files and good instructions for how to build all the containers. It's sprinkled throughout the repositories, which is kind of bad, when they have these cross-repo dependencies. But I'm not willing/able to tackle that at the moment.

                        • footfaults [none/use name]
                          ·
                          2 years ago

                          Like, they didn't use a tool like Helm, or frankly, make their docker-compose files modular enough to work for both local testing, and production (usually this is done via environment variables and templating) so that they work for both. Instead there's just copies of docker-compose files littered throughout the repos.

                          I do this kind of stuff for a living, but I can't force everyone to do things the right way.

                        • tagen
                          ·
                          1 year ago

                          deleted by creator

                          • footfaults [none/use name]
                            ·
                            2 years ago

                            Order doesn't matter. They just both have to be built. You probably built the backend, and didn't finish/wait for the frontend.

                            • tagen
                              ·
                              1 year ago

                              deleted by creator

                              • footfaults [none/use name]
                                ·
                                2 years ago

                                So, that's an issue with the last command in the build_docker.sh where it tries to do a docker-compose up -d - which really it shouldn't do. Building a docker image and running/invoking docker-compose should be two different operations. I don't know why the docker-compose command is mixed in.

                                • tagen
                                  ·
                                  1 year ago

                                  deleted by creator

                                  • footfaults [none/use name]
                                    ·
                                    2 years ago

                                    You're welcome. At some point after my $JOB quiets down, I will maybe go in and clean up the docker mess and replace it with my far more opinionated way of doing things, but with better documentation for people just getting started with the code. Because it should have a clear README and instructions for how to get things up and running, with no gotchas or mystery

        • sexywheat [none/use name]
          ·
          2 years ago

          In the same way that thexbear deviated from the official release of lemmy, minecraft mods will deviate you from the official release cycle of minecraft, and if you deviate too far (or one of your mods stops getting active development) then you get stuck in an old version with no way to upgrade due to dependence on custom/legacy code.

    • TrashGoblin [he/him, they/them]
      ·
      2 years ago

      I think the plan now (per the transparency post) is to drop merge plans per se, implement the features in Hexbear that Lemmy is still missing, and migrate Hexbear's data to mainline Lemmy once it's possible.