Your want your media volume to link to your media folder outside of docker.
Below volume definition line is outside:inside
-v /home/user/media/data:/media
docker run -d
–name my_container
-v my_volume:/path/inside/container
image_name
I name my machines after my cats.
Question about the viewing habits data. Is this only related to the Free Ad Supported Streaming content Plex pushes or are they also tracking viewing habits of users personal libraries?
Can you list a few examples?
I like your setup.
My stack is R730s with MD1200 DAS. Using about 380watts.
Is your nas on Ext4?
That’s a power efficient setup, nice!
Interesting. I was able to find a few big Lemmy communities on Mastodon. But I couldn’t find my tiny instance community.
I wonder what I need to do to get my own instance to federate with Mastodon?
They killed Google Domains?!
How does Void Linux rate on the security and privacy front compared to the top recommendations in this thread?
I also demand answers. Should I be able to see Mastodon posts via my Lemmy/wefwef?
Restic to multiple repositories, local and remote.
I think it depends on your scale. If homelab stuff docker is awesome IMO.
+1 vote for Thunderbird
In the article. Free Ad Supported sTreaming = FAST.
All the embedded LIVE TV or Movies from Plex are all ad supported streaming media not coming from your own Plex server.
I don’t want any of that on my Plex instance and the focus on FAST has been a clear shift in strategy.
Fully agree
I agree. Run everything you want and then when you see performance degradation then you’ll know the limits of your hardware based on your workloads.
You already have the NUC so why not push it’s limits? The alternative is to try and guestimate your workload needs and buy matching hardware… which is very difficult.