Hi all!

For those who are using a very small, limited-RAM VPS (smaller than 4GB), how are you finding keeping Lemmy up to date?

I’m doing each component piecemeal, and on my 2GB RAM VPS I couldn’t finish lemmy backend’s cargo build, just too much RAM required even with 1.5GB of swap (VPS provider is really going to enjoy that, I’m sure)

I did the production build on a machine at home and copied the lemmy_server over. Seems to be fine, but… rust or lemmy seem to have some massive resource requirements on the build.

  • Dessalines
    1•3 years ago

    I would strongly recommend against using anything but the already-built docker images for production. Newest versions of the code from the git can easily break compatibility. Our current code version has breaking changes in activitypub compatibility for example, that won’t work with the official images.

    • KinetixOP
      0•3 years ago

      I will have to keep my eyes open for that potential, as I’m not interested in putting docker on my systems. Though… I can easily stick with the tags to stay away from the breakage, no?

      I guess having the docker image solves the building resource issue.

      • @nutomic@lemmy.mlM
        0•3 years ago

        As long as you stay with our releases there should be no problems. But building and running without Docker is just extra work for you really.

        • KinetixOP
          1•3 years ago

          I think it’s a great opportunity, to be honest. Good to get to know how each component is built & runs.

          Docker is another ‘thing’ that one has to work at, too - leaving the extra complexity on your system and hoping for the best isn’t my idea of managing a system very well. Though, the packaging definitely has it’s conveniences.