> For the complete documentation index, see [llms.txt](https://jvlflame.gitbook.io/2.5.5/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jvlflame.gitbook.io/2.5.5/installation/install-javinizer-web-gui.md). # Install Javinizer (Web GUI) {% hint style="warning" %} **The GUI version of Javinizer may not be updated at the same rate as the CLI version.** {% endhint %} **The Javinizer GUI supports two install methods:** * [Docker](/2.5.5/installation/install-javinizer-web-gui.md#docker) * [Windows](/2.5.5/installation/install-javinizer-web-gui.md#windows) ## Docker Docker is the preferred method for installing and running the Javinizer Web GUI. The Javinizer image lives on [Docker Hub](https://hub.docker.com/repository/docker/jvlflame/javinizer). To quickstart, run the following command: ``` docker run --name javinizer -p 8600:8600 -d jvlflame/javinizer:latest ``` ### Persisting Data You will most likely want to persist settings data when running Javinizer within Docker. {% hint style="warning" %} **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.** {% endhint %} ### Docker Run Example ``` docker run --name javinizer -p 8600:8600 -v path/to/jvSettings.json:/home/jvSettings.json -d jvlflame/javinizer:latest ``` To persist your settings file, create a copy of the [settings file](https://github.com/jvlflame/Javinizer/blob/master/src/Javinizer/jvSettings.json) and bind mount the file: * `/home/jvSettings.json` To persist other settings files, set paths in your location settings. ![](https://1908076997-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLpB-ZaZqqyXVu4FpgN%2F-MMF-JXlpoGs_hK_bNAZ%2F-MMF-vYXg3nKcUXintWR%2Fimage.png?alt=media\&token=080b94ae-f4f4-47a3-897f-9b3238bf460c) ### Docker Desktop Example If you are using Docker Desktop with Hyper-V, you will want to make use of "File Sharing". In your Docker Desktop settings, add your mount directories and click Apply & Restart. Using WSL2, you will have to use a different method. ![](https://1908076997-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLpB-ZaZqqyXVu4FpgN%2F-MPlOOMwLR11h9-TKHtA%2F-MPlP2N7rSp8HtabTzRF%2Fimage.png?alt=media\&token=b72893c2-9260-4c9b-90ea-f325fb1f6c9e) With the example path of `C:\javinizer\docker`, I can now run the following command to persist the PowerShell Universal appdata: ``` docker run --name Javinizer -p 8600:8600 -v C:/javinizer/docker/jvSettings.json:/home/jvSettings.json jvlflame/javinizer:latest ``` ### Unraid Example If you want to use Javinizer via Docker on Unraid, here is an example template. ![Unraid](https://1908076997-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLpB-ZaZqqyXVu4FpgN%2F-MUgm7X2uHhyJDT6t7uP%2F-MUgmtv1JZY-a2Rjnpeh%2Fimage.png?alt=media\&token=3ca02832-100f-4130-80d1-8e713444fa63) ## Windows The Javinizer GUI can be installed on Windows. ### Install Dependencies You will need to install the Javinizer CLI and its dependencies. View the instructions on the [**Install Javinizer (CLI)**](/2.5.5/installation/install-javinizer-cli.md) page for details. This includes: * PowerShell Core * Python 3 * googletrans module * google\_trans\_new module * pillow module * MediaInfo (optional) * Javinizer module After installing Javinizer and its dependencies, **run PowerShell as administrator** and run the following command to install PowerShell Universal and other required modules. ``` Javinizer -InstallGUI ``` Once this installation has completed and both PowerShell and Python modules are installed, run the following command to open the GUI page. ``` # Runs by default on port 8600 Javinizer -OpenGUI ``` ``` # (Optional) You can set a custom port Javinizer -OpenGUI -Port 8080 ``` The `-OpenGUI` command will automatically open a page to`http://localhost:/` which contains the Javinizer GUI. ## Use Network Paths If the files you want to sort live on a network path in Windows, it is likely that you will need to re-mount your network drives within an admin scope. Run PowerShell or CMD as administrator and run the following command to mount your network drive. Substitute `g:` for the drive letter of your choice. ``` # Network drive net use g: \\server\share # Network drive that requires authentication net use g: \\server\share /user: ``` If you are still unable to see your network drive after mounting via an administrator prompt, you can mount your drive directly from the **Admin** tab in the Javinizer GUI. ![Successful network drive mount](https://1908076997-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLpB-ZaZqqyXVu4FpgN%2F-MQV2i5z762YnH_d_baT%2F-MQV2zYLtlzAhXOnakIF%2Fnet%20use.png?alt=media\&token=38892973-4ab5-4bbc-aa3d-1c3277eab623) ![Confirm that your network drive is visible via Javinizer](https://1908076997-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLpB-ZaZqqyXVu4FpgN%2F-MQV2i5z762YnH_d_baT%2F-MQV337fH29qCMJx3w90%2Fls.png?alt=media\&token=7e81d90b-8fde-403e-964d-24544cb46146) ## Add PowerShell 7 Environment If your PowerShell Universal did not automatically detect your PowerShell 7 installation, you can add it manually. 1. Navigate to the PowerShell Universal admin page 1. `http://localhost:/admin` 2. Username is `admin` with any password 2. On the sidebar, navigate to Settings -> Environments 3. Click the **Add** button 4. Fill in the **Name** and **Path** entries and click **OK** 5. On the sidebar, navigate to Dashboards -> Dashboards and edit the existing Javinizer dashboard entry 6. Set the environment to the new environment that you created ![](https://1908076997-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MLpB-ZaZqqyXVu4FpgN%2F-MQnZXJzqLmLsDP__ibe%2F-MQn_FDsNrO6EncmodXH%2Fimage.png?alt=media\&token=e4f370bf-079e-4939-8604-893ad7f06e98)