I’ve been working with the two suggested LemmyNet installation methods; Docker and Ansible. Neither are too wild of a setup, but they aren’t plug and play docker-compose-like, either.

I want to run a LemmyNet on a subdomain; lemmy.domain.com, and use nginx-proxy-manager to point traffic in the right direction, but it will be on the same local IP… some port changes will need to be made.

Is anyone running their own instances? Have suggestions or tips with things that helped you lean up a lemmy.subnet?

Cheers!!

  • pAULIE42o
  • . . . . . . . . . . .
  • /s
  • grouvie@lemmy.help
    2·
    1 year ago

    Hosting at Hetzner.

    • 3x CX41 -> 4 vCPU, 16GB RAM
    • 3x CX21 -> 2 vCPU, 4GB RAM
    • 1x CPX21 -> 3 vCPU, 4GB RAM

    Server configuration may appear a bit weird. I have the storage managed with longhorn. It’s not on the nodes, but mounted to them.

    • ultraHQ@lemmy.one
      0·
      1 year ago

      Nice, thanks for sharing! I’d like to try to integrate this with a CI/CD pipeline as I’ll be forking Lemmy with slight modifications that I’d like to make. Do you have any experience with this?

      • grouvie@lemmy.help
        0·
        1 year ago

        Absolutely! Today I made significant improvements to the lemmy_help guide, which means deploying lemmy should now be even more straightforward. Personally, I have successfully deployed my instance using argoCD. However, I’m also aware of someone else who has been using my helm charts to deploy lemmy with fluxCD.