Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
I have had a mesh setup end up with one device throwing old files across the entire mesh and it took me an entire hour to fix and get replication working correctly again. So right now I have all devices connecting to my plex server only, no mesh. If a device updates, it goes to my server then propagates to my other devices.
This lets every device be able to update a file or pull back updates. Because the plex server is the sole adjudicator of changes, I dont have to deal with any file mismatches or keep a single source as read-only.
Ah, I get it, thanks :)
I tried doing it that way at first, but because my wife's laptop is only used occasionally, I was getting the errors from that. At the moment the mesh is working for me.
Next week might be different though ๐