Install Javinizer (CLI)
Last updated
Last updated
There are currently two ways to install the CLI:
This method requires that you install all dependencies by yourself
PowerShell Core (Version 6+) is required for use of the Javinizer module. I recommend using the latest stable release of PowerShell 7.
Python 3 is required for the use of some features of the Javinizer module:
Image cropping (Poster Image)
Text translation
CloudFlare scraping (deprecated)
Python needs to be added to your system PATH. Select the "Add Python 3.9 to PATH" checkbox during installation. After installing Python, you will need to install three Python modules via pip.
Open an administrator PowerShell or CMD console and run the following command.
Follow install instructions for your specific Linux distribution. Javinizer calls all Python commands on Linux using python3
and modules will need to be installed using pip3
.
MediaInfo (CLI) is required for the use of some features of the Javinizer module:
Parse media file metadata (resolution, etc.)
There are two ways to install Javinizer:
The recommended method to use Javinizer is installing the module via PSGallery. For power users, downloading releases manually or importing the module may be your choice instead.
Please choose either one method as they are mutually exclusive. If you are not sure, please install with PSGallery only.
Run PowerShell 7 as administrator.
Install the module via the Install-Module
command and then restart your shell.
Run PowerShell 7 and run the following command:
You can check if Javinizer has successfully installed from PowerShell 7 and run the following command:
You can run the latest cli docker build (CLI tags are labeled as [version]-cli
).
You will most likely want to persist settings data when running Javinizer within Docker.
Your sort input and output paths should be using the same bind mount, otherwise moving files between them will take an extended amount of time.
The following command will provide you with a Powershell interpreter which you can then use to execute Javinizer's CLI commands with your media mapped to /mnt
while keeping the persistency of your jvSettings.json
.
/home/jvSettings.json
To persist other settings files, set paths in your location settings:
"location.thumbcsv": ""
"location.genrecsv": ""
"location.uncensorcsv": ""
"location.historycsv": ""
"location.tagcsv": ""
"location.log": "",
The MediaInfo executable will need to be added to your system PATH. Generic instructions .
or clone the repository and extract the files to a directory of your choice.
Note that the CLI docker build versions are meant to give you a Powershell interpreter with Javinizer pre-installed. You would then need to refer the to execute the appropriate commands. Also note that you will now need to refer to mount points inside the container. For example, if you mounted -v /path/to/media:/mnt
then you will need to refer /mnt
and not /path/to/media
.
If you want to run it on the NAS without using the CLI, it's recommended to use the version instead.
To persist your settings file, create a copy of the and bind mount the file: