Are there any technical/performance reasons why I couldn’t create an instance for myself and host a Plex server off of the same machine at home?

I’m fairly new to self-hosting in general, so any insight would be appreciated!

EDIT: I completely forgot to mention that this would be for a Mastodon instance, not for Lemmy.

  • @vikingEnglish
    5•6 months ago

    Lemmy often racks up hundreds of gigabytes in logs and other crap, chokes up the hard drive, and then force restarts the server. Not fun for something you use to stream media from. Takes quite some tuning to get it sorted.

    If we are talking about two virtual machines on the same physical server with dedicated storage allocation, that shouldn’t matter.

    • ShadowEnglish
      8•6 months ago

      Lol Wat.

      Op, just budget 200gb for lemmy and you’ll be fine. Our entire lemmy.ca server is only using 100gb. It’ll be a good learning experience!

      Also, check out jellyfin as a possible alternative to plex.

      • veeeOPEnglish
        2•6 months ago

        I should have specified that I was interested in creating a Mastodon instance, not Lemmy, but I’m glad to know that I could do that should I want to build one.

        I’ve looked into Jellyfin as a secondary service. At the moment my parents have gotten used to navigating Plex and having them re-learn something new over the phone is…not something I have the energy or time for lol

        • ShadowEnglish
          1•6 months ago

          Images aren’t federated, but their thumbnails are stored in your instance. You can prune those though as needed.

    • @redcalcium@lemmy.instituteEnglish
      2•6 months ago

      It’s true, it logs a huge amount of stuff due to federation chatter. If you run it with docker, be sure to setup log rotation. I think the recommended lemmy ansible installation set the rotation to 50MB x 4 files. Or just /dev/null it.