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.
I run Lemmy, Plex, and a bunch of other services from a desktop in my basement. It works great. The Lemmy docker setup is a little finicky but works well once you get it.
My bad, I forgot to specify that I’d like to create a Mastodon instance, not Lemmy. Though it’s good to hear that people are having success.
deleted by creator
The cheapest digitalocean VPS doesn’t have enough ram to host lemmy these days, especially after v0.19 update significantly increase database ram consumption. You’ll have to use a vps with at least 4 GB of ram which will cost $24/mo. If you only want to spend $5/mo for that kind of VPS, you’ll have to dig into lowendtalk.com to find some VPS deals from a somewhat reputable providers.
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.
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.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.
Doesn’t all the federated images take up a shit ton of space?