I’m considering starting a Lemmy instance with a limited federation model, and one of the things I’m thinking about from the start is how to support and maintain it as it grows, while spending as little attention as possible on the technical side of infrastructure management itself.

Because of that, I’m especially interested in hearing from admins who host Lemmy instances, particularly larger ones. I’d like to understand what your actual workflow looks like in practice: how you organize administration, what methodologies you use, how you handle backups, data recovery, upgrades, monitoring, and infrastructure maintenance in general. I’m also interested in whether there are any best practices or operational patterns that have proven reliable over time.

From what I’ve found so far, the official Lemmy documentation on backup and restore seems reasonably good for small instances, but as the instance grows, more nuances and complications appear. So ideally, I’d like to find or assemble something closer to a real guideline or runbook based on practices that are actually used by admins running larger instances.

If you run or have run a Lemmy instance, especially one that had to scale beyond a small personal or experimental setup, I’d really appreciate hearing about your experience. Even brief notes, links to documentation, internal checklists, or descriptions of what has and hasn’t worked for you would be very useful.

  • Meldrik@lemmy.wtf
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 day ago

    Host PieFed instead.

    With that said, I host Lemmy.wtf, which is a rather small instance.

    Proxmox > LXC > Docker.

    The container has 6 vcores and 6GB RAM.

    Backups are handled by Proxmox.

    • nachitima@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      4 hours ago

      Hey, thanks for sharing this.

      I’m trying to get a clearer picture of what a reliable Lemmy backup/restore setup looks like in practice, especially for self-hosting.

      A few things I’d be curious about in your setup:

      • Are your Proxmox backups enough on their own, or do you also make separate Postgres dumps?
      • Are you backing up the whole container/VM image, or do you also separately keep pictrs data, config files, secrets, reverse proxy config, etc.?
      • Have you actually tested a full restore from backup onto another machine? If yes, did it come back cleanly?
      • Do you do local-only backups, or also offsite copies?
      • When you update Lemmy, do you rely on rollback from snapshots if something breaks, or do you have another recovery path?

      Main thing I’m trying to understand is whether Proxmox-only backups are “good enough” operationally, or whether people still end up needing app-level backups too.

      Sorry if some of these questions are a bit basic or oddly specific — I’m using AI to help gather as much real-world Lemmy hosting experience as possible, and it generated most of these follow-up questions for me.

      • Meldrik@lemmy.wtf
        link
        fedilink
        English
        arrow-up
        1
        ·
        48 minutes ago

        Backups of the LXC container has been enough, but I’m thinking about doing a secondary backup of the DB itself.

        Everything runs in the same container.

        I have restored the container many times. Also, every time there’s an update, I backup the container first and then I can restore it if something breaks.

        I have 2 local backups and then 3 remotely at Hetzner.