This field can contain multiple rewriting rules. The rewrite field can be defined for each individual trigger. Triggers can receive paths from any source: A remote server, a Docker container and the local file system. They allow you to translate paths between a trigger's / target's perspective and the processor's perspective.īefore you begin, make sure you understand how regular expressions work! \ Make sure you know how capture groups work, as these are used for the to field. That's where rewrite rules come into play. Some are used in Docker containers, others run on host OS, it can be a big mess! Triggers, targets and the processor all live in different contexts. Overview ¶Īutoscan is split into three distinct modules:
If you need to debug certain Autoscan behaviour, either add the -v flag for debug mode or the -vv flag for trace mode to get even more details about internal behaviour. If you want autoscan to be globally available, move it to /bin or /usr/local/bin. You should now have a binary with the name autoscan in the root directory of the project.
#Emby server manual manual#
Autoscan does not rely on manual trash deletion when connected to Plex.A-Train does not support RClone Crypt remotes.A-Train, Autoscan's Google Drive integration, only supports Shared Drives and requires Service Account authentication.In addition, this rewrite introduces a more modular approach and should be easy to extend in the future. Wait, what happened to Plex Autoscan? Well, Autoscan is a rewrite of the original Plex Autoscan written in the Go language. Autoscan integrates with Sonarr, Radarr, Lidarr and Google Drive to fetch changes in near real-time without relying on the file system. Autoscan replaces the default Plex and Emby behaviour for picking up file changes on the file system.
0 kommentar(er)
