Starting the container¶
docker run --rm \ --name autoscan \ -p 3030:3030 \ -e PUID=1000 \ -e PGID=1000 \ -e UMASK=002 \ -e TZ="Etc/UTC" \ -e PLEX_LOGIN="" \ -e PLEX_PASSWORD="" \ -v /<host_folder_config>:/config \ cr.hotio.dev/hotio/autoscan
version: "3.7" services: autoscan: container_name: autoscan image: cr.hotio.dev/hotio/autoscan ports: - "3030:3030" environment: - PUID=1000 - PGID=1000 - UMASK=002 - TZ=Etc/UTC - PLEX_LOGIN - PLEX_PASSWORD volumes: - /<host_folder_config>:/config
PLEX_PASSWORD are not empty and the file
/config/plex.token does not exist, an attempt is made to get a Plex token for Autoscan.
|Tag||Description||Version||Commit SHA||Commit Message||Last Updated||Age|
The above table reflects the current state of the Git repository. The docker repository is mainly in sync, unless builds fail or commits are pushed for which no builds are started (usually indicated with
[skip ci] in the commit message). You can click on the tag's name to go to its corresponding branch on GitHub, clicking the commit sha brings you to the git diff of that commit.
Using a secure Plex connection¶
If you want to keep using secure connections within Plex, but don't wanna buy your own domain and keep the connection between Autoscan and Plex inside of their Docker network. Follow the below procedure.
xxxxxxxxxxxxxx with your token) and look for a url that looks like
https://10-1-0-100.xxxxxxxxxxxxx.plex.direct:32400. That url can be used in your Autoscan plex target. You should however give the Plex container a static IP if you don't wanna do this every 5 minutes.