Slowly exploring the lemmy ecosystem, since I don’t want to use reddit, and was wondering if selfhosting would be a good idea?

  • chris@l.roofo.cc
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Yes. I am immune from the beehaw/lemmy.world drama or similar. I can block instances as I please and I can tinker with my instance.

      • deejay4am@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Eh, kinda. lemmy doesn’t have super great moderation tools yet, and the influx of users on lemmy.world and lemmy.ml included people posting some content that was against beehaw’s moderation guidelines. Rather than deal with being overwhelmed without much option, they decided to temporarily defederate until there was a clear path to resolving the issue (i.e. better mod tools).

        I think people are making it out to be a bigger deal than it really is, and those flames are probably being stoked by the trolls.

        There are plenty of “no actually assault weapons are good for society” and “actually Ukraine is the aggressor” groypers around now, but I guess that just means Lemmy is getting popular enough to attract the masses - which in the end is a net positive.

    • 𝘋𝘪𝘳𝘬@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I can tinker with my instance.

      I didn’t even find a SANE way to set it up with Docker without having to tinker with the instance. I just want a container not generating half a dozen of other containers and volumes.

      • Fauxreigner@lemmy.fauxreigner.net
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        A single container for everything gets away from the point of containerization. If you have a single container for lemmy-ui, lemmy backend, and postgres, you need to rebuild that container whenever any one of those applications gets an update, and they could start to interfere with each other. Keeping them in separate containers makes everything a lot cleaner, it just requires something like docker compose to put it all together.

        Did you try the Ansible install? Provided you’re installing onto a supported Debian/Ubuntu version, I found it fairly straightforward.

        • 𝘋𝘪𝘳𝘬@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I see the container thing a little different. A container should contain all things that are needed to run the containered application (and if it is a web application then exposing one single port). Creating containers should not create multiple other containers ( have no other use for) or networks, or volumes.

          • underisk@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            They aren’t all one application. Many of the parts can be swapped out for alternatives, shared with other services, or just excluded entirely. They can also be scaled separately which is important because not all of them need to scale at the same rate.

            What you want is explicitly what docker-compose exists to do.