![]() Now with infuse this would still work if used the plex library, but it doesn’t show the tv shows properly which is the big let down, so I can’t pick up where I left off on another operating system - if I use direct sharing (as I would in Plex) then it shows fine which suggests its an infuse/plex compatibility issue - i am slowly getting some showing correctly but that is only by using TMM and saving NFO files, etc in every folder which under Plex and Kodi, I never have to do and this is just wasting storage space on my server with un-necessary content.Īlso Infuse has a better layout than Plex on Apple TV as it provides more of an apple interface compared to plex. This is done by passing the user ID and group ID to the container via the USER_ID and GROUP_ID environment variables.Yeh, Plex is good for library management and as a LPM I won’t be removing it especially as I use it on Android devices and TV’s - I originally got infuse as saw it said it worked with audio passthrough which as with other apps on apple it don’t - plus plex provides me with information on what is playing, etc and means I can start on Apple TV and move to Shield TV, Android devices or LG TV’s and picked up where I left off. To avoid any problem, you can specify the user tinyMediaManager should run as. This could prevent the container from properly accessing files and folders on the shared volume and vice versa. For example, the user within the container may not exist on the host or does not match the right user on the host. When using using data volumes (-v flags for /data and media), permissions issues can occur between the host and the container (tinyMediaManager). This image should work on any x8664 device. This image includes all needed components (up to date libmediainfo, FFmpeg, ) for the best experience. See below for an example how to use this. tinyMediaManager offers an (experimental) official docker image based on Debian Buster (for maximum compatibility). ID of the group tinyMediaManager runs as. See below for an example how to use this. This image offers some special configuration parameters which can be passed to docker by using environment variables Variable You need read/write access to all mapped volumes! Configuration If you do not map this out of the container, all your data/settings will be lost on an upgrade of tinyMediaManager /data: where all local data of tinyMediaManager will be stores.You should map the following folders to a volume/folder on the host: E.g.:ĭocker run \ -name =tinymediamanager \ -p 4000:4000 \ -v :/data \ -v :/media/movies \ -v :/media/tvshows \Īfter starting the container, you can access tinyMediaManager via Data volumes Map local volumes/folders/mounts to /media/xxx where all media will be accessed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |