[{"_1":2,"_165":-5,"_166":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_140":141},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_131":-5,"_132":11,"_133":17,"_134":11,"_135":-5,"_136":11,"_137":-5,"_138":139},"canonicalUrl","https://hub.docker.com/r/mtlott/clutch/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","mtlott","reponame","clutch","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2020-10-06T11:08:27.526156Z","description","An automated EDL splicer","is_private","last_updated","2020-10-11T11:46:09.13081Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",891,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Docker container for Clutch\n\nThis is a Docker container for Clutch.\n\nClutch provides a bridge between a DVR which outputs EDL files such as [Channels-DVR](https://channels.com) and an automated version of [HandBrake](https://github.com/jlesage/docker-handbrake).\n\nAt this time the GUI provides only status information through a web-based VNC session.\n\nThe fully automated functionality provides watch folders: drop files into a watch folder and let Clutch process them without any user interaction. Or have an upstream processing stage write to the watch folder.\n\n---\n[![Clutch logo](https://images.weserv.nl/?url=raw.githubusercontent.com/mtlott/Clutch/master/images/clutch-logo.jpg&w=400)](https://github.com/mtlott/clutch/)[![Clutch](https://dummyimage.com/400x110/ffffff/575757&text=Clutch)](https://github.com/mtlott/clutch/)\n\nClutch is an EDL (Edit Decision List) splicer tool which utilizes ffmpeg to cut segments from a video file without reencoding.\n\nClutch is based on the amazing work of jlesage on [docker-handbrake](https://github.com/jlesage/docker-handbrake)\n\n---\n## Table of Content\n\n * [Docker container for Clutch](#docker-container-for-clutch)\n * [Table of Content](#table-of-content)\n * [Quick Start](#quick-start)\n * [Usage](#usage)\n * [Environment Variables](#environment-variables)\n * [Data Volumes](#data-volumes)\n * [Ports](#ports)\n * [Changing Parameters of a Running Container](#changing-parameters-of-a-running-container)\n * [Docker Compose File](#docker-compose-file)\n * [Docker Image Update](#docker-image-update)\n * [User/Group IDs](#usergroup-ids)\n * [Accessing the GUI](#accessing-the-gui)\n * [Security](#security)\n * [SSVNC](#ssvnc)\n * [Certificates](#certificates)\n * [VNC Password](#vnc-password)\n * [Reverse Proxy](#reverse-proxy)\n * [Routing Based on Hostname](#routing-based-on-hostname)\n * [Routing Based on URL Path](#routing-based-on-url-path)\n * [Shell Access](#shell-access)\n * [Automatic Video Conversion](#automatic-video-conversion)\n * [Multiple Watch Folders](#multiple-watch-folders)\n * [Hooks](#hooks)\n * [Temporary Conversion Directory](#temporary-conversion-directory)\n * [Nightly Builds](#nightly-builds)\n * [Debug Builds](#debug-builds)\n * [Support or Contact](#support-or-contact)\n\n## Quick Start\n\n**NOTE**: The Docker command provided in this quick start is given as an example\nand parameters should be adjusted to your need.\n\nLaunch the Clutch docker container with the following command:\n```\ndocker run -d \\\n --name=clutch \\\n -p 5800:5800 \\\n -v /docker/appdata/clutch:/config:rw \\\n -v $HOME:/storage:ro \\\n -v $HOME/Clutch/watch:/watch:rw \\\n -v $HOME/Clutch/output:/output:rw \\\n mtlott/clutch\n```\n\nWhere:\n - `/docker/appdata/clutch`: This is where the application stores its configuration, log and any files needing persistency.\n - `$HOME`: This location contains files from your host that need to be accessible by the application.\n - `$HOME/Clutch/watch`: This is where videos to be automatically converted are located.\n - `$HOME/Clutch/output`: This is where automatically converted video files are written.\n\nBrowse to `http://your-host-ip:5800` to access the Clutch GUI.\nFiles from the host appear under the `/storage` folder in the container.\n\n## Usage\n\n```\ndocker run [-d] \\\n --name=clutch \\\n [-e =]... \\\n [-v :[:PERMISSIONS]]... \\\n [-p :]... \\\n jlesage/clutch\n```\n| Parameter | Description |\n|-----------|-------------|\n| -d | Run the container in the background. If not set, the container runs in the foreground. |\n| -e | Pass an environment variable to the container. See the [Environment Variables](#environment-variables) section for more details. |\n| -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the [Data Volumes](#data-volumes) section for more details. |\n| -p | Set a network port mapping (exposes an internal container port to the host). See the [Ports](#ports) section for more details. |\n\n### Environment Variables\n\nTo customize some properties of the container, the following environment\nvariables can be passed via the `-e` parameter (one for each variable). Value\nof this parameter has the format `=`.\n\n| Variable | Description | Default |\n|----------------|----------------------------------------------|---------|\n|`USER_ID`| ID of the user the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`GROUP_ID`| ID of the group the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`SUP_GROUP_IDS`| Comma-separated list of supplementary group IDs of the application. | (unset) |\n|`UMASK`| Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation. By default, this variable is not set and the default umask of `022` is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl | (unset) |\n|`TZ`| [TimeZone] of the container. Timezone can also be set by mapping `/etc/localtime` between the host and the container. | `Etc/UTC` |\n|`KEEP_APP_RUNNING`| When set to `1`, the application will be automatically restarted if it crashes or if a user quits it. | `0` |\n|`APP_NICENESS`| Priority at which the application should run. A niceness value of -20 is the highest priority and 19 is the lowest priority. By default, niceness is not set, meaning that the default niceness of 0 is used. **NOTE**: A negative niceness (priority increase) requires additional permissions. In this case, the container should be run with the docker option `--cap-add=SYS_NICE`. | (unset) |\n|`CLEAN_TMP_DIR`| When set to `1`, all files in the `/tmp` directory are deleted during the container startup. | `1` |\n|`DISPLAY_WIDTH`| Width (in pixels) of the application's window. | `1280` |\n|`DISPLAY_HEIGHT`| Height (in pixels) of the application's window. | `768` |\n|`SECURE_CONNECTION`| When set to `1`, an encrypted connection is used to access the application's GUI (either via a web browser or VNC client). See the [Security](#security) section for more details. | `0` |\n|`VNC_PASSWORD`| Password needed to connect to the application's GUI. See the [VNC Password](#vnc-password) section for more details. | (unset) |\n|`X11VNC_EXTRA_OPTS`| Extra options to pass to the x11vnc server running in the Docker container. **WARNING**: For advanced users. Do not use unless you know what you are doing. | (unset) |\n|`ENABLE_CJK_FONT`| When set to `1`, open-source computer font `WenQuanYi Zen Hei` is installed. This font contains a large range of Chinese/Japanese/Korean characters. | `0` |\n|`AUTOMATED_CONVERSION_KEEP_SOURCE`| When set to `0`, a video that has been successfully converted is removed from the watch folder. | `1` |\n|`AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION`| When set to `ignore`, a non-video file found in the watch folder is ignored. If set to `copy`, a non-video file is copied as-is to the output folder. | `ignore` |\n|`AUTOMATED_CONVERSION_NON_VIDEO_FILE_EXTENSIONS`| Space-separated list of file extensions to be considered as not being videos. Most non-video files are properly rejected by Clutch. However, some files, like images, are convertible by Clutch even if they are not video files. | `jpg jpeg bmp png gif txt nfo` |\n|`AUTOMATED_CONVERSION_OUTPUT_DIR`| Root directory where converted videos should be written. | `/output` |\n|`AUTOMATED_CONVERSION_OUTPUT_SUBDIR`| Subdirectory of the output folder into which converted videos should be written. By default, this variable is not set, meaning that videos are saved directly into `/output/`. If `Home/Movies` is set, converted videos will be written to `/output/Home/Movies`. Use the special value `SAME_AS_SRC` to use the same subfolder as the source. For example, if the video source file is `/watch/Movies/mymovie.mkv`, the converted video will be written to `/output/Movies/`. | (unset) |\n|`AUTOMATED_CONVERSION_SOURCE_STABLE_TIME`| Time (in seconds) during which properties (e.g. size, time, etc) of a video file in the watch folder need to remain the same. This is to avoid processing a file that is being copied. | `5` |\n|`AUTOMATED_CONVERSION_SOURCE_MIN_DURATION`| Minimum title duration (in seconds). Shorter titles will be ignored. This applies only to video disc sources (ISO file, `VIDEO_TS` folder or `BDMV` folder). | `10` |\n|`AUTOMATED_CONVERSION_CHECK_INTERVAL`| Interval (in seconds) at which the automatic video converter checks for new files. | `5` |\n|`AUTOMATED_CONVERSION_MAX_WATCH_FOLDERS`| Maximum number of watch folders handled by the automatic video converter. | `5` |\n|`CLUTCH_DEBUG`| Setting this to `1` enables Clutch debug logging for both the GUI and the automatic video converter. For the latter, the increased verbosity is reflected in `/config/log/hb/conversion.log` (container path). For the GUI, log messages are sent to `/config/log/hb/clutch.debug.log` (container path). **NOTE**: When enabled, a lot of information is generated and the log file will grow quickly. Make sure to enable this temporarily and only when needed. | (unset) |\n|`AUTOMATED_CONVERSION_NO_GUI_PROGRESS`| When set to `1`, progress of videos converted by the automatic video converter is not shown in the Clutch GUI. | `0` |\n|`AUTOMATED_CONVERSION_HANDBRAKE_CUSTOM_ARGS`| Custom arguments to pass to Clutch when performing a conversion. | (unset) |\n|`AUTOMATED_CONVERSION_INSTALL_PKGS`| Space-separated list of Alpine Linux packages to install. This is useful when the automatic video converter's hooks require tools not available in the container image. See https://pkgs.alpinelinux.org/packages?name=&branch=v3.9&arch=x86_64 for the list of available Alpine Linux packages. | (unset) |\n|`AUTOMATED_CONVERSION_OVERWRITE_OUTPUT`| Flag to allow the final destination file to be overwritten if it already exists. Useful in pipeline scenarios where the input file presented to Clutch may change based on upstream processing. | `0` |\n\n### Data Volumes\n\nThe following table describes data volumes used by the container. The mappings\nare set via the `-v` parameter. Each mapping is specified with the following\nformat: `:[:PERMISSIONS]`.\n\n| Container path | Permissions | Description |\n|-----------------|-------------|-------------|\n|`/config`| rw | This is where the application stores its configuration, log and any files needing persistency. |\n|`/storage`| ro | This location contains files from your host that need to be accessible by the application. |\n|`/watch`| rw | This is where videos to be automatically converted are located. |\n|`/output`| rw | This is where automatically converted video files are written. |\n\n### Ports\n\nHere is the list of ports used by the container. They can be mapped to the host\nvia the `-p` parameter (one per port mapping). Each mapping is defined in the\nfollowing format: `:`. The port number inside the\ncontainer cannot be changed, but you are free to use any port on the host side.\n\n| Port | Mapping to host | Description |\n|------|-----------------|-------------|\n| 5800 | Mandatory | Port used to access the application's GUI via the web interface. |\n| 5900 | Optional | Port used to access the application's GUI via the VNC protocol. Optional if no VNC client is used. |\n\n### Changing Parameters of a Running Container\n\nAs seen, environment variables, volume mappings and port mappings are specified\nwhile creating the container.\n\nThe following steps describe the method used to add, remove or update\nparameter(s) of an existing container. The generic idea is to destroy and\nre-create the container:\n\n 1. Stop the container (if it is running):\n```\ndocker stop clutch\n```\n 2. Remove the container:\n```\ndocker rm clutch\n```\n 3. Create/start the container using the `docker run` command, by adjusting\n parameters as needed.\n\n**NOTE**: Since all application's data is saved under the `/config` container\nfolder, destroying and re-creating a container is not a problem: nothing is lost\nand the application comes back with the same state (as long as the mapping of\nthe `/config` folder remains the same).\n\n## Docker Compose File\n\nHere is an example of a `docker-compose.yml` file that can be used with\n[Docker Compose](https://docs.docker.com/compose/overview/).\n\nMake sure to adjust according to your needs. Note that only mandatory network\nports are part of the example.\n\n```yaml\nversion: '3'\nservices:\n clutch:\n image: mtlott/clutch\n build: .\n ports:\n - \"5800:5800\"\n volumes:\n - \"/docker/appdata/clutch:/config:rw\"\n - \"$HOME:/storage:ro\"\n - \"$HOME/Clutch/watch:/watch:rw\"\n - \"$HOME/Clutch/output:/output:rw\"\n```\n\n## Docker Image Update\n\nIf the system on which the container runs doesn't provide a way to easily update\nthe Docker image, the following steps can be followed:\n\n 1. Fetch the latest image:\n```\ndocker pull mtlott/clutch\n```\n 2. Stop the container:\n```\ndocker stop clutch\n```\n 3. Remove the container:\n```\ndocker rm clutch\n```\n 4. Start the container using the `docker run` command.\n\n### Synology\n\nFor owners of a Synology NAS, the following steps can be used to update a\ncontainer image.\n\n 1. Open the *Docker* application.\n 2. Click on *Registry* in the left pane.\n 3. In the search bar, type the name of the container (`mtlott/clutch`).\n 4. Select the image, click *Download* and then choose the `latest` tag.\n 5. Wait for the download to complete. A notification will appear once done.\n 6. Click on *Container* in the left pane.\n 7. Select your Clutch container.\n 8. Stop it by clicking *Action*->*Stop*.\n 9. Clear the container by clicking *Action*->*Clear*. This removes the\n container while keeping its configuration.\n 10. Start the container again by clicking *Action*->*Start*. **NOTE**: The\n container may temporarily disappear from the list while it is re-created.\n\n### unRAID\n\nFor unRAID, a container image can be updated by following these steps:\n\n 1. Select the *Docker* tab.\n 2. Click the *Check for Updates* button at the bottom of the page.\n 3. Click the *update ready* link of the container to be updated.\n\n## User/Group IDs\n\nWhen using data volumes (`-v` flags), permissions issues can occur between the\nhost and the container. For example, the user within the container may not\nexists on the host. This could prevent the host from properly accessing files\nand folders on the shared volume.\n\nTo avoid any problem, you can specify the user the application should run as.\n\nThis is done by passing the user ID and group ID to the container via the\n`USER_ID` and `GROUP_ID` environment variables.\n\nTo find the right IDs to use, issue the following command on the host, with the\nuser owning the data volume on the host:\n\n id \n\nWhich gives an output like this one:\n```\nuid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)\n```\n\nThe value of `uid` (user ID) and `gid` (group ID) are the ones that you should\nbe given the container.\n\n## Accessing the GUI\n\nAssuming that container's ports are mapped to the same host's ports, the\ngraphical interface of the application can be accessed via:\n\n * A web browser:\n```\nhttp://:5800\n```\n\n * Any VNC client:\n```\n:5900\n```\n\n## Security\n\nBy default, access to the application's GUI is done over an unencrypted\nconnection (HTTP or VNC).\n\nSecure connection can be enabled via the `SECURE_CONNECTION` environment\nvariable. See the [Environment Variables](#environment-variables) section for\nmore details on how to set an environment variable.\n\nWhen enabled, application's GUI is performed over an HTTPs connection when\naccessed with a browser. All HTTP accesses are automatically redirected to\nHTTPs.\n\nWhen using a VNC client, the VNC connection is performed over SSL. Note that\nfew VNC clients support this method. [SSVNC] is one of them.\n\n[SSVNC]: http://www.karlrunge.com/x11vnc/ssvnc.html\n\n### SSVNC\n\n[SSVNC] is a VNC viewer that adds encryption security to VNC connections.\n\nWhile the Linux version of [SSVNC] works well, the Windows version has some\nissues. At the time of writing, the latest version `1.0.30` is not functional,\nas a connection fails with the following error:\n```\nReadExact: Socket error while reading\n```\nHowever, for your convenience, an unofficial and working version is provided\nhere:\n\nhttps://github.com/jlesage/docker-baseimage-gui/raw/master/tools/ssvnc_windows_only-1.0.30-r1.zip\n\nThe only difference with the official package is that the bundled version of\n`stunnel` has been upgraded to version `5.49`, which fixes the connection\nproblems.\n\n### Certificates\n\nHere are the certificate files needed by the container. By default, when they\nare missing, self-signed certificates are generated and used. All files have\nPEM encoded, x509 certificates.\n\n| Container Path | Purpose | Content |\n|---------------------------------|----------------------------|---------|\n|`/config/certs/vnc-server.pem` |VNC connection encryption. |VNC server's private key and certificate, bundled with any root and intermediate certificates.|\n|`/config/certs/web-privkey.pem` |HTTPs connection encryption.|Web server's private key.|\n|`/config/certs/web-fullchain.pem`|HTTPs connection encryption.|Web server's certificate, bundled with any root and intermediate certificates.|\n\n**NOTE**: To prevent any certificate validity warnings/errors from the browser\nor VNC client, make sure to supply your own valid certificates.\n\n**NOTE**: Certificate files are monitored and relevant daemons are automatically\nrestarted when changes are detected.\n\n### VNC Password\n\nTo restrict access to your application, a password can be specified. This can\nbe done via two methods:\n * By using the `VNC_PASSWORD` environment variable.\n * By creating a `.vncpass_clear` file at the root of the `/config` volume.\n This file should contain the password in clear-text. During the container\n startup, content of the file is obfuscated and moved to `.vncpass`.\n\nThe level of security provided by the VNC password depends on two things:\n * The type of communication channel (encrypted/unencrypted).\n * How secure the access to the host is.\n\nWhen using a VNC password, it is highly desirable to enable the secure\nconnection to prevent sending the password in clear over an unencrypted channel.\n\n**ATTENTION**: Password is limited to 8 characters. This limitation comes from\nthe Remote Framebuffer Protocol [RFC](https://tools.ietf.org/html/rfc6143) (see\nsection [7.2.2](https://tools.ietf.org/html/rfc6143#section-7.2.2)). Any\ncharacters beyond the limit are ignored.\n\n## Reverse Proxy\n\nThe following sections contain NGINX configurations that need to be added in\norder to reverse proxy to this container.\n\nA reverse proxy server can route HTTP requests based on the hostname or the URL\npath.\n\n### Routing Based on Hostname\n\nIn this scenario, each hostname is routed to a different application/container.\n\nFor example, let's say the reverse proxy server is running on the same machine\nas this container. The server would proxy all HTTP requests sent to\n`clutch.domain.tld` to the container at `127.0.0.1:5800`.\n\nHere are the relevant configuration elements that would be added to the NGINX\nconfiguration:\n\n```\nmap $http_upgrade $connection_upgrade {\n\tdefault upgrade;\n\t'' close;\n}\n\nupstream docker-clutch {\n\t# If the reverse proxy server is not running on the same machine as the\n\t# Docker container, use the IP of the Docker host here.\n\t# Make sure to adjust the port according to how port 5800 of the\n\t# container has been mapped on the host.\n\tserver 127.0.0.1:5800;\n}\n\nserver {\n\t[...]\n\n\tserver_name clutch.domain.tld;\n\n\tlocation / {\n\t proxy_pass http://docker-clutch;\n\t}\n\n\tlocation /websockify {\n\t\tproxy_pass http://docker-clutch;\n\t\tproxy_http_version 1.1;\n\t\tproxy_set_header Upgrade $http_upgrade;\n\t\tproxy_set_header Connection $connection_upgrade;\n\t\tproxy_read_timeout 86400;\n\t}\n}\n\n```\n\n### Routing Based on URL Path\n\nIn this scenario, the hostname is the same, but different URL paths are used to\nroute to different applications/containers.\n\nFor example, let's say the reverse proxy server is running on the same machine\nas this container. The server would proxy all HTTP requests for\n`server.domain.tld/clutch` to the container at `127.0.0.1:5800`.\n\nHere are the relevant configuration elements that would be added to the NGINX\nconfiguration:\n\n```\nmap $http_upgrade $connection_upgrade {\n\tdefault upgrade;\n\t'' close;\n}\n\nupstream docker-clutch {\n\t# If the reverse proxy server is not running on the same machine as the\n\t# Docker container, use the IP of the Docker host here.\n\t# Make sure to adjust the port according to how port 5800 of the\n\t# container has been mapped on the host.\n\tserver 127.0.0.1:5800;\n}\n\nserver {\n\t[...]\n\n\tlocation = /clutch {return 301 $scheme://$http_host/clutch/;}\n\tlocation /clutch/ {\n\t\tproxy_pass http://docker-clutch/;\n\t\tlocation /clutch/websockify {\n\t\t\tproxy_pass http://docker-clutch/websockify/;\n\t\t\tproxy_http_version 1.1;\n\t\t\tproxy_set_header Upgrade $http_upgrade;\n\t\t\tproxy_set_header Connection $connection_upgrade;\n\t\t\tproxy_read_timeout 86400;\n\t\t}\n\t}\n}\n\n```\n## Shell Access\n\nTo get shell access to a the running container, execute the following command:\n\n```\ndocker exec -ti CONTAINER sh\n```\n\nWhere `CONTAINER` is the ID or the name of the container used during its\ncreation (e.g. `crashplan-pro`).\n\n## Automatic Video Conversion***\n\nThis container has an automatic video converter built-in. This is useful to\nbatch-convert videos without user interaction.\n\nBasically, files copied to the `/watch` container folder are automatically\nedited by Clutch based on the supplied EDL file.\n\nSee the [Environment Variables](#environment-variables) section for details\nabout setting environment variables.\n\n**NOTE**: Converted videos are stored, by default, to the `/output` folder of\nthe container.\n\n**NOTE**: The status and progression of conversions performed by the automatic\nvideo converter can be seen from both the GUI and the container's log.\nContainer's log can be obtained by executing the command\n`docker logs clutch`, where `clutch` is the name of the container. Also,\nfull details about the conversion are stored in `/config/log/hb/conversion.log`\n(container path).\n\n### Multiple Watch Folders\n\nIf needed, up to 4 additionnal watch folders can be used:\n - `/watch2`\n - `/watch3`\n - `/watch4`\n - `/watch5`\n\nThis is useful in scenarios where videos need to be converted by different\nlater stages of the video processing pipeline. For example, one could use \na watch folder for movies and another watch folder for TV shows, both having \ndifferent output directories which are monitored by different downstream post processors.\n\nBy default, additional watch folders inherits the same settings has the main one\n(`/watch`). A setting for a particular watch folder can be overrided by adding\nits index to the corresponding environment variable name.\n\nFor example, to set the Clutch output directory in `/watch2`,\nthe environment variable `AUTOMATED_CONVERSION_OUTPUT_DIR_2` is used.\n`AUTOMATED_CONVERSION_OUTPUT_DIR_3` is used for `/watch3`, and so on.\n\nAll settings related to the automatic video converter can be overrided for each\nadditional watch folder:\n - `AUTOMATED_CONVERSION_SOURCE_STABLE_TIME`\n - `AUTOMATED_CONVERSION_SOURCE_MIN_DURATION`\n - `AUTOMATED_CONVERSION_OUTPUT_DIR`\n - `AUTOMATED_CONVERSION_OUTPUT_SUBDIR`\n - `AUTOMATED_CONVERSION_KEEP_SOURCE`\n - `AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION`\n - `AUTOMATED_CONVERSION_OVERWRITE_OUTPUT`\n\n### Hooks\n\nCustom actions can be performed using hooks. Hooks are shell scripts executed\nby the automatic video converter.\n\n**NOTE**: Hooks are always invoked via `/bin/sh`, ignoring any shebang the\nscript may have.\n\nHooks are optional and by default, no one is defined. A hook is defined and\nexecuted when the script is found at a specific location.\n\nThe following table describe available hooks:\n\n| Container location | Description | Parameter(s) |\n|--------------------|-------------|--------------|\n| `/config/hooks/pre_conversion.sh` | Hook executed before the beginning of a video conversion. | The first argument is the path of the converted video. The second argument is the path to the source file. |\n| `/config/hooks/post_conversion.sh` | Hook executed when the conversion of a video file is terminated. | The first parameter is the status of the conversion. A value of `0` indicates","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",234020727,"orgData","recentTags",[87,125],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",8478391,"full_size",131762593,"id",120225172,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:80c1b286457525c65cc73eb86685b1dc168a4da387ee6ac6f0137c6a17ae293d","features","","last_pulled","2026-09-26T18:59:21.018579937Z","last_pushed","2020-10-11T11:46:08Z","os","linux","os_features","os_version","size","variant","2020-10-11T11:46:08.685332Z","last_updater","last_updater_username","media_type","latest","repository",9972399,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_88":40,"_89":90,"_91":92,"_93":126,"_95":127,"_46":129,"_115":90,"_116":29,"_117":52,"_53":130,"_119":120,"_121":105,"_122":129,"_123":62,"_124":17},120435567,[128],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"2020-10-11T11:46:07.921332Z","v1.0.0","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":142,"_149":150,"_138":163,"_164":11},{"_36":143,"_38":144,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":145,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":146,"_75":11,"_76":148,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":147},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_151":152,"_153":-5,"_154":-5,"_155":156},"count",2,"next","previous","results",[157,160],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":158,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[159],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},{"_88":40,"_89":90,"_91":92,"_93":126,"_95":161,"_46":129,"_115":90,"_116":29,"_117":52,"_53":130,"_119":120,"_121":105,"_122":129,"_123":62,"_124":17},[162],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

mtlott/clutch

Tags for mtlott/clutch