I’m nervous about the creation of a symlink in there — if one of the docker containers with read/write to the data share can follow that symlink, now any vulnerability in that container app can achieve malicious access to PMS which isn’t containerized.
There’s a “principle of least surprise” in monkeying with other people’s storage mappings, doubly important when it comes to paths and security.
Sounds like PMSLibShare would have been ideal, agree about not asking for admin creds to get it. There are (unfortunately?) ways one can drop a script to run as admin to make that one available (think autorun.sh), but that seems both rude and fragile.
Looking at what’s in the folder we want to access over a share:
Cache/
Codecs/
Crash Reports/
Diagnostics/
Logs/
Media/
Metadata/
plexmediaserver.pid
Plug-ins/
Plug-in Support/
Preferences.xml
Scanners/
Thumbnails/
What about:
PlexSysAdmin/
- Appropriately a little scary
- Sets the expectation that if you poke around in it without knowing what you’re doing you could break something
- Doesn’t sound like a good place to put Movies or TV
- Does not conflict with recommendation to name media data paths
datain docker setup best practices - Does tell you this is a reasonable to look for all that kind of stuff in the list
