Does anyone run their own Lemmy instance on a pi? How was the process of setting it up? Were there any pitfalls? How is performance?

  • blotz@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 year ago

    Im looking at setting up a lemmy instance on a rpi3 with cloudflared tunnel! I’m curious to see if anyone else has done this and how it was.

    Edit: I’ll give it a whirl and hopefully post an update from my new instance later!

  • Jeena@jemmy.jeena.net
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    I don’t think there should be any problems, lemmy is a fairly lightweight web application, it’s compiled so no big overhead of some runtime like ruby in case of mastodon. I haven’t tried it on a raspberry Pi, but on my server the load is always just around 0.1

    The only bottleneck I could think of was Postgres, but I’ve been running postgres on raspberry pies without any problems before too.

  • marsara9@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I was able to get it setup, main things to watch out for:

    • Don’t use the provided docker compose file. Or more precisely don’t build from source and lookup the correct image tag on docker hub first.
    • The documentation was a bit confusing. This isn’t really specific for the Pi but since I was creating a compose file from scratch some of the steps listed didn’t quite explain all of the details.

    I only used it for testing purposes, but performance was fine (on a Pi4 4gb). Note I only ever had one user.

  • GustavoM@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    Not yet, but I’m planning to. And I don’t think there will be any “pitfalls” at all other than your microsd dying in a couple of months rather than years due to it getting hammered constantly by API requests, etc.

    • r00ty@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      You could plug in a USB SSD or HDD and make sure the DB and other regularly written data goes there. That would pretty much remove the problem.

      I would wonder how well it would perform. The limited memory and cpu power surely would make database access not great under even moderate load.

    • blotz@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Are you asking me what i plan to set the cap to? I guess just me. I cant see anyone else wanting to run off a pi from my house and there are so many other instances to join.

      • Path23@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        I’m a newbie here but what would be the benefit of running an instance just for yourself?

        • HunterHog@pathfinder.social
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          The ability to host your own data - both for privacy, and insurance that the instance you host your account in won’t suddenly disappear.

          • thegreenguy@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            I would also add that Lemmy is part of the fediverse, meaning it is federated. Federation means all instances “talk” to all instances (unless they defederate), so you aren’t limited only to the content on one instance (or in some cases not even Lemmy, case in point: I’m posting this from my kbin.social account).

            • Adama@kbin.social
              link
              fedilink
              arrow-up
              0
              ·
              1 year ago

              What happens to posts/comments and any media/content that is hosted on a server that just goes away (for example if I created one virtually and then deleted it or if a sdcard on a pi is corrupted)

              • marsara9@lemmy.world
                link
                fedilink
                arrow-up
                2
                ·
                1 year ago

                If you upload an image to that server, the image will be gone. Your comments will still exist on other federated instances, assuming that instance was federated in the first place. But any replies to those communities will not propagate once the hosting instance is offline.

                For example assume you have 3 instances, A, B, and C. You have an account on A and create a post to a community on A. At some point A goes away, but those posts and that community will still exist on B and C. So you create a new account on B, and reply to one of those posts… users on C won’t be able to see those replies as A isn’t there to broadcast those replies out. And if someone on C creates a new post on that community from A, you wouldn’t be able to see it on B either.

                P.S. The same is true if A just decides to defederate instead of shutting down. (other than the images and accounts would still exist obviously).

        • poVoq@slrpnk.net
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Basically the limit would be the speed of the database and the drive it runs on. If you connect a SATA SSD via usb3 it shouldn’t be too bad. Can’t tell you exact figures but a few hundred users is probably ok if you don’t expect the site to be super responsive.

          • YellowtoOrange@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            10
            ·
            1 year ago

            Thanks. Might be useful for there to be a table outling diffrent hardware configs and acceptable user loads as more people people consider creating instances.

            • adora@kbin.social
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              its difficult because different users have different usage patterns.
              for example, two users who never post and are never online at the same time really take no resources from each other. they are effectively “one” user.

              one user who posts 10gb of content a day, and is constantly posting would be equivalent to hundreds of “normal” users.