diff --git a/.github/workflows/publish-wiki.yml b/.github/workflows/publish-wiki.yml
new file mode 100644
index 000000000..6ac14f167
--- /dev/null
+++ b/.github/workflows/publish-wiki.yml
@@ -0,0 +1,33 @@
+name: Publish ARM Wiki Update
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - arm_wiki/**
+  pull_request_review:
+    types: [submitted]
+  gollum:
+
+env:
+  GIT_AUTHOR_NAME: Actionbot
+  GIT_AUTHOR_EMAIL: actions@github.com
+
+permissions:
+  contents: write
+
+jobs:
+  job-sync-docs-to-wiki:
+    runs-on: ubuntu-latest
+    if: github.event_name != 'gollum'
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v2
+      - name: Sync arm docs to wiki
+        uses: newrelic/wiki-sync-action@main
+        with:
+          source: arm_wiki
+          destination: wiki
+          token: ${{ secrets.ARM_WIKI_TOKEN }}
+          gitAuthorName: ${{ env.GIT_AUTHOR_NAME }}
+          gitAuthorEmail: ${{ env.GIT_AUTHOR_EMAIL }}
\ No newline at end of file
diff --git a/arm_wiki/ARM-Development-Tools.md b/arm_wiki/ARM-Development-Tools.md
new file mode 100644
index 000000000..ad00f0691
--- /dev/null
+++ b/arm_wiki/ARM-Development-Tools.md
@@ -0,0 +1,179 @@
+## Overview
+To support development of ARM, some of the more tedious and repetitious development tasks have been wrapped up into the ARM Development Tools. The developer tools (devtools) are designed to help out anyone contributing to ARM and save time when testing out any changes being made.
+
+To run devtools, navigate to the arm devtools folder and run the python file, armdevtools.py.
+
+_Note: if the file is not executable, run `chown u+x armdevtools.py`_
+
+`cd devtools`
+
+## Running devtools
+
+There are various commands available to the developer, as detailed below. The general output from the devtools follows:
+
+```
+INFO: <detail of the command being run>
+INFO: Going to stop ARMUI - requesting sudo <requested to stop any ARM UI currently running>
+INFO: ARM UI stopped    [Ok]
+INFO: -------------------------------------
+INFO: <command(s) the script runs>
+INFO: <Script status on running the command_     [Ok]
+INFO: -------------------------------------
+INFO: <command(s) the script runs>
+INFO: <Script status on running the command>     [Ok]
+INFO: Going to restart ARMUI - requesting sudo _requested to restart the ARM UI_
+INFO: ARM UI started    [Ok]
+```
+
+### [-h] Help
+The below shows the list of available commands devtools provides.
+
+```
+./armdevtools.py -h
+usage: armdevtools.py [-h] [-b B] [-dr DR] [-db_rem] [-qa] [-pr] [-v]
+
+Automatic Ripping Machine Development Tool Scripts
+
+options:
+  -h, --help  show this help message and exit
+  -b B        Name of the branch to move to, example -b v2_devel
+  -dr DR      Docker rebuild post ARM code update. Requires docker run script path to run.
+  -db_rem     Database tool - remove current arm.db file
+  -qa         QA Checks - run Flake8 against ARM
+  -pr         Actions to run prior to committing a PR against ARM on github
+  -v          ARM Dev Tools Version
+```
+
+### [-b B] Git branch change
+Running this command provides a simple way to stop the ARM UI (if running on bare metal) and checkout a new branch. Whilst checking out a new git branch is a simple task, if the current ARM UI is not stopped prior to changing branches, strange things can occur. This script automates the change and aims to prevent spooky action at a distance.
+
+```
+./armdevtools.py -b v2_devel
+INFO: Change the current git branch to - v2_devel
+INFO: Going to stop ARMUI - requesting sudo
+INFO: ARM UI stopped    [Ok]
+M       arm-dependencies
+Branch 'v2_devel' set up to track remote branch 'v2_devel' from 'origin'.
+Switched to a new branch 'v2_devel'
+INFO: ARM branch: v2_devel checked out
+INFO: Going to restart ARMUI - requesting sudo
+INFO: ARM UI started    [Ok]
+```
+
+### [-dr DR] Docker Rebuild
+Following any code changes to ARM, testing the changes in the docker image can be a tedious process. This command automates some of the process to make that change easier. To run this command, a bash script needs to be provided that will, when run will create the ARM docker image. For more details on the docker run configuration, refer to [Building ARM docker image from source](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Building-ARM-docker-image-from-source)
+
+_Note: executing this script requires docker permissions, otherwise it will fail._
+
+Running this command executes the following docker commands.
+1. Stops the ARM container
+2. Removes the ARM container
+3. Rebuilds the ARM container
+4. Starts the ARM container, using the provided bash file/script
+
+```
+./armdevtools.py -dr /home/arm/armdocker.bash 
+INFO: Going to stop ARMUI - requesting sudo
+INFO: ARM UI stopped    [Ok]
+INFO: Rebuilding docker image post ARM update
+INFO: -------------------------------------
+INFO: Executing: docker stop automatic-ripping-machine
+Error response from daemon: No such container: automatic-ripping-machine
+INFO: ARM container stopped     [Ok]
+INFO: -------------------------------------
+INFO: Executing: docker container rm automatic-ripping-machine
+Error: No such container: automatic-ripping-machine
+INFO: ARM Docker container deleted      [Ok]
+INFO: -------------------------------------
+INFO: Executing: docker build -t automatic-ripping-machine /opt/arm
+Sending build context to Docker daemon   34.2MB
+Step 1/21 : FROM automaticrippingmachine/arm-dependencies:1.1.1 AS base
+ ---> 601d89529745
+...
+steps removed to reduce wiki size
+...
+Step 21/21 : WORKDIR /home/arm
+ ---> Running in 6ed2590d5d46
+Removing intermediate container 6ed2590d5d46
+ ---> 58b643c79d04
+Successfully built 58b643c79d04
+Successfully tagged automatic-ripping-machine:latest
+INFO: ARM Docker container rebuilt      [Ok]
+INFO: -------------------------------------
+INFO: Executing: /home/arm/armdocker.bash
+ec1f1c857f498c16f5149efaf305ed78828247577dd2c637c4c2bfd81525a449
+INFO: ARM Docker container running      [Ok]
+INFO: Going to restart ARMUI - requesting sudo
+INFO: ARM UI started    [Ok]
+```
+
+### [-db_rem] Remove ARM Database
+During development, there may come a time when testing requires removing the ARM database to confirm functionality and graceful exit states when no database exists. Whilst a simple command to remove the database, removing whilst ARM is running is not a good idea, again the whole spooky action at a distance. This command handles stopping the UI, removing the database and starting the UI again.
+
+_Note: This command won't stop a docker container, and removing the ARM.db file whilst running is not a good idea._
+
+_Note 2: Removing the arm.db file requires the user running the script to have ownership of the file, otherwise the script will fail._
+
+```
+./armdevtools.py -db_rem
+INFO: Removing the ARM DB file
+INFO: Going to stop ARMUI - requesting sudo
+INFO: ARM UI stopped    [Ok]
+INFO: ARM DB /home/arm/db/arm.db removed        [Ok]
+INFO: Going to restart ARMUI - requesting sudo
+INFO: ARM UI started    [Ok]
+```
+
+
+### [-qa] Run Flake8 Check
+When a new commit is made against ARM, the [github workflows](https://github.com/automatic-ripping-machine/automatic-ripping-machine/tree/main/.github/workflows) are automatically run against the commit, to ensure the new codes quality and functionality. Running the QA check devtool command runs the same Flake8 check against the '/opt/arm' folder and files prior to commencing any commits and potentially failing the QA checks.
+For more details of how Flake8 works can be found at [https://flake8.pycqa.org/en/latest/](https://flake8.pycqa.org/en/latest/).
+Running the qa check executes the below command, and if all is good will return no results, as shown below.
+
+`flake8 /opt/arm/arm --max-complexity=15 --max-line-length=120 --show-source --statistics`
+
+```
+./armdevtools.py -qa
+INFO: Going to stop ARMUI - requesting sudo
+INFO: ARM UI stopped    [Ok]
+INFO: Running quality checks against ARM - /opt/arm
+INFO: -------------------------------------
+INFO: Executing: flake8 /opt/arm/arm --max-complexity=15 --max-line-length=120 --show-source --statistics
+INFO: ARM QA check completed    [Ok]
+INFO: Going to restart ARMUI - requesting sudo
+INFO: ARM UI started    [Ok]
+```
+
+### [-pr] Pre-PR Actions
+Executes a list of actions required to bring any ARM code up to scratch prior to raising a new PR.
+Currently this runs:
+- Update Git submodule (ARM dependencies)
+
+```
+./armdevtools.py -pr
+INFO: Going to stop ARMUI - requesting sudo
+INFO: ARM UI stopped    [Ok]
+INFO: Running scripts to bring ARM up to date
+INFO: -------------------------------------
+INFO: Executing: cd .. & git submodule update --remote
+remote: Enumerating objects: 7, done.
+remote: Counting objects: 100% (7/7), done.
+remote: Compressing objects: 100% (7/7), done.
+remote: Total 7 (delta 2), reused 0 (delta 0), pack-reused 0
+Unpacking objects: 100% (7/7), 3.01 KiB | 770.00 KiB/s, done.
+From https://github.com/automatic-ripping-machine/arm-dependencies
+ * [new branch]      dependabot/pip/sqlalchemy-2.0.6 -> origin/dependabot/pip/sqlalchemy-2.0.6
+   6caa6fb..8029c3e  main                            -> origin/main
+Successfully rebased and updated detached HEAD.
+Submodule path '../arm-dependencies': rebased into '8029c3ebbe0406d07cf09e277eb17f6978986ee1'
+INFO: ARM submodule updated     [Ok]
+INFO: Going to restart ARMUI - requesting sudo
+INFO: ARM UI started    [Ok]
+```
+
+### [-v] Devtools version
+Reports the current version of devtools
+```
+./armdevtools.py -v
+armdevtools.py 0.2
+```
\ No newline at end of file
diff --git a/arm_wiki/ARM-ui-skins.md b/arm_wiki/ARM-ui-skins.md
new file mode 100644
index 000000000..93edc9431
--- /dev/null
+++ b/arm_wiki/ARM-ui-skins.md
@@ -0,0 +1,23 @@
+## For v2.4 or newer
+
+ARM makes use of [Bootstrap](https://getbootstrap.com) for alot of the heavy lifting with the ARM ui. One of the benefits of using this is that it allows users to easily customise all of the ARM ui thanks to themes/skins for bootstrap.
+
+You can get great selection of skins/Themes from here [bootswatch](https://bootswatch.com)
+
+The process for updating the Skin/Theme is pretty simple
+   - Find the Theme you like
+   - Download its bootstrap.min.css file
+   - Place the file inside (arm install path)/arm/ui/static/css
+   - You should overwrite the previous file
+   - Clear your browser cache (Shift + F5 on some browsers CTRL + F5 on others)
+   - Thats it!
+
+
+The default path for ARM unless you have changed it is `/opt/arm/`
+This would mean the default full path for the bootsrap.min.css file would be `/opt/arm/arm/ui/static/css/bootstrap.min.css`
+
+## For versions older than v2.4
+
+Follow the above steps, there is an additional step that is required
+
+ - You will need to change the downloaded file name to bootstrap.spacelab.css and then copy it to the above directory. The only difference being that the final full path would be ``/opt/arm/arm/ui/static/css/bootstrap.spacelab.css``
diff --git a/arm_wiki/ARM-workflow-diagram.md b/arm_wiki/ARM-workflow-diagram.md
new file mode 100644
index 000000000..551bb7432
--- /dev/null
+++ b/arm_wiki/ARM-workflow-diagram.md
@@ -0,0 +1,3 @@
+
+
+![Workflow Diagram](https://github.com/muckngrind4/arm_wiki/blob/master/images/arm.png)
\ No newline at end of file
diff --git a/arm_wiki/Building-ARM-docker-image-from-source.md b/arm_wiki/Building-ARM-docker-image-from-source.md
new file mode 100644
index 000000000..e59ea1106
--- /dev/null
+++ b/arm_wiki/Building-ARM-docker-image-from-source.md
@@ -0,0 +1,86 @@
+## Building an ARM Docker Image  
+
+### :bangbang:This is not compatible with the snap version of docker!:bangbang:
+
+This requires you to build an image from source. 
+
+### Pre-requisites
+1. Instructions tested based on a new Ubuntu 20.04 LTS minimal install 
+2. Create the arm user and set a password
+3. Install Docker, an editor such as Atom or VS Codium, lsscsi, and any other needed utilities as desired  
+4. Setup all of your optical drives so that the arm (non-root) user can mount them. Run `lsscsi -g` to verify their mountpoints if you're unsure.  
+  -run `sudo mkdir -p /mnt/dev/sr0` and repeat for each device, e.g., sr1, sr2, etc  
+  -edit fstab and add an entry for each drive, incrementing the sr* number for each  
+  `sudo nano /etc/fstab`     
+  `/dev/sr0  /mnt/dev/sr0  udf,iso9660  users,noauto,exec,utf8  0  0`
+
+### Add the arm user and group (Recommended)
+This help with permission issues, and isolates A.R.M to its own user.
+```
+# Create the arm group
+groupadd arm
+# Create the arm user
+useradd -m arm -g arm
+# Set the new arm users password
+passwd arm
+# Add the user to the cdrom,video groups
+usermod -aG cdrom,video arm
+```
+
+### Build the image:
+`git clone https://github.com/automatic-ripping-machine/automatic-ripping-machine.git arm`  
+
+`cd arm`
+
+`docker build -t automatic-ripping-machine .`
+
+### Create the container:
+Remember to modify this for YOUR unique configuration!
+ ```
+docker run -d \
+    -p "8080:8080" \
+    -e ARM_UID="<id -u arm>" \
+    -e ARM_GID="<id -g arm>" \
+    -v "<path_to_arm_user_home_folder>:/home/arm" \
+    -v "<path_to_music_folder>:/home/arm/Music" \
+    -v "<path_to_logs_folder>:/home/arm/logs" \
+    -v "<path_to_media_folder>:/home/arm/media" \
+    -v "<path_to_config_folder>:/etc/arm/config" \
+    --device="/dev/sr0:/dev/sr0" \
+    --device="/dev/sr1:/dev/sr1" \
+    --device="/dev/sr2:/dev/sr2" \
+    --device="/dev/sr3:/dev/sr3" \
+    --privileged \
+    --restart "always" \
+    --name "automatic-ripping-machine"
+```
+### Finally -  Open localhost:8080/setup, then login to the account
+
+The default username and password:
+username: admin
+password: password
+
+** It is strongly recommended you change this using the change password page **
+A.R.M should now be fully setup, and ripping should start when a disc is inserted.
+
+----
+
+#### Notes
+The ARM_UID(1000) and ARM_GID(1000) should exist outside the container. This helps against any permission issues.
+
+It is recommended when passing in a device to pass in both labels you get from `lsscsi -g`
+For example, if `lsscsi -g` outputs 
+
+```
+[2:0:0:0]    cd/dvd  NECVMWar VMware SATA CD00 1.00  /dev/sr0   /dev/sg1 
+[32:0:0:0]   disk    VMware,  VMware Virtual S 1.0   /dev/sda   /dev/sg0 
+```
+You should pass in 
+```
+    --device="/dev/sr0:/dev/sr0" \
+    --device="/dev/sg1:/dev/sg1" \
+```
+This isn't required, arm will still work, but it will not perform as well as it can.
+
+### Troubleshooting
+Please see the [docker troubleshooting page](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Docker-Troubleshooting)
diff --git a/arm_wiki/Change-Log.md b/arm_wiki/Change-Log.md
new file mode 100644
index 000000000..9895377be
--- /dev/null
+++ b/arm_wiki/Change-Log.md
@@ -0,0 +1,279 @@
+## Pre-release - V2.6.4
+* drop github actor as it breaks packages by @1337-server in https://github.com/automatic-ripping-machine/automatic-ripping-machine/pull/528
+* Update to 2.6.4 by @1337-server in https://github.com/automatic-ripping-machine/automatic-ripping-machine/pull/536
+
+Fixes 
+- 1337-server/automatic-ripping-machine#201
+- 1337-server/automatic-ripping-machine#203
+- 1337-server/automatic-ripping-machine#207
+- 1337-server/automatic-ripping-machine#180 now fully saves
+- [Fix ARM UI tests](https://github.com/1337-server/automatic-ripping-machine/commit/dfcd69b211b91abf921489e11f7d9ad5e4121eaf) Now correctly moves file, so testing doesn't fail
+- Added test to check for breakages for Ubuntu 18
+- Fix for scheduled actions not building docker image correctly
+- Adds support for sr0-sr9 in docker
+- Re-adds support for MakeMKV key in docker
+### Python version bumps
+- [Bump beautifulsoup4 from 4.10.0 to 4.11.1](https://github.com/1337-server/arm-dependencies/commit/901f64457d77673a2d96cad7adc91cbab5ee327c)
+- [Bump soupsieve from 2.3.1 to 2.3.2.post1](https://github.com/1337-server/arm-dependencies/commit/df63d3e206fda5b417f3287c7f56cae628a7d318)
+- [Bump cffi from 1.15.0 to 1.15.1 ](https://github.com/1337-server/arm-dependencies/commit/f3aca97bc978d2e3357f32b41783044bb4091835)
+- [Bump flask-wtf from 1.0.0 to 1.0.1 ](https://github.com/1337-server/arm-dependencies/commit/24283a8979380f0011ef0b810641c6fe7f7b50b7)
+- [Bump xmltodict from 0.12.0 to 0.13.0 ](https://github.com/1337-server/arm-dependencies/commit/cdc92461cf1c527ab210f683a52e3a8f583a0280)
+- [Bump sqlalchemy from 1.4.32 to 1.4.39](https://github.com/1337-server/arm-dependencies/commit/e9c08f6f790d30b2d396c303396784b7dd65f874)
+- [Bump psutil from 5.9.0 to 5.9.1 ](https://github.com/1337-server/arm-dependencies/commit/4c830553911d050f72776a699aa1d5c879672ab0)
+- [Bump apprise from 0.9.7 to 0.9.9 ](https://github.com/1337-server/arm-dependencies/commit/3d1e4e5fe426fdc15fededade8d32c6bfdb8ea34)
+- [Bump urllib3 from 1.26.9 to 1.26.10 ](https://github.com/1337-server/arm-dependencies/commit/00ab6de0f7c51fed12303708bee7b0f30988fcb1)
+- [Bump certifi from 2021.10.8 to 2022.6.15 ](https://github.com/1337-server/arm-dependencies/commit/80c4cc36357a1a8e54020c7214a891c35f3ee079)
+- [Bump actions/setup-python from 2 to 4 ](https://github.com/1337-server/arm-dependencies/commit/b478e5ef251e6ed0ac86893037090b526e4e9369)
+
+
+## v2.6.0 > v2.6.3
+   - Fixed Ubuntu 18 support
+   - Added submodule for arm dependencies
+   - Added port param to install script
+   - Fixed 1337-server/automatic-ripping-machine#126
+   - Fixed 1337-server/automatic-ripping-machine#143
+   - Fixed 1337-server/automatic-ripping-machine#154
+   - Fixed 1337-server/automatic-ripping-machine#155
+   - Fixed 1337-server/automatic-ripping-machine#157
+   - Fix for modal not showing fixperms text
+   - Added helper note/comment for makemkv codes
+   - Added git version to logging
+   - import_movies() refactored to be a little more readable
+   - Messages on database.html now follow the scroll position
+   - Refactored save_settings() to comply with sonarcloud
+   - send_movies.html now mostly client side, to save long page load times
+   - yes/no database buttons are now hidden when getting success/failed jobs 
+   - MakeMKV now fully respects the minlength from cfg (MakeMKV was ignoring anything below 2 mins)
+   - Music disc now eject on success or failure (eject removed from default abcde.config)
+   - Converted all js strings to template strings
+
+## v2.6.0
+   - Fixes #129 (Jobs arent removed from index when completed)
+   - Added MakeMKV progress in armui
+   - Added function to automatically update MakeMKV beta key
+   - Restructuring of makemkv.py, code cleanup and formatting
+   - Refactoring js code to reduce warnings/errors
+   - Refactoring of makemkv.py
+       - Fix bug in file sorting
+       - Added noqa tags for variables that aren't being used
+       - Removing unused variables from makemkv
+       - Nicer printing of the logging statement
+       - Make sure each title is transcoded in order
+
+   - Updated Ubuntu install scripts
+       - ---------- FIXES ----------
+       - fixed command to run under arm user & properly run without hanging script
+       - fixed errors and added logic
+       - Fixed permissions issue
+       - fixed out of order parameters
+       - fix for broken service start
+       - fix for 1337-server/automatic-ripping-machine issue #111 (Permissions error when editing the ARM Settings after fresh install)
+       - fix continuing error calling aplay in scripts
+       - ---------- ADDED ----------
+       - Added pycharm-community install
+       - Added ALSA install to script to avoid breakage on Ubuntu Server instances
+       - Added handling for arm group/user already existing
+       - Added installs for lsscsi and net-tools
+       - Added coloration to logging statements
+       - Added Markdown v3.3.4 explicitly to requirements.txt, to fix breaking change caused by 3.3.5 (see Python-Markdown/markdown#1203)
+       - Added logic to prevent duplicating fstab entries
+       - Added handling harness for script options
+       - Added logic to run proper installation function
+       - Added call for launch_setup
+       - Added now shows the ip of the site that's now running
+       - ---------- MOVED ----------
+       - Moved dev environment installation location
+       - Moved heredocs to custom files
+       - Moved checkout command a better spot
+       - ---------- OTHER ----------
+       - pycharm runs as "other", so the 777 is needed
+       - implemented install_arm_dev_env
+       - implemented launch_setup
+       - hard-coding path since the user folder is already created
+       - Refactored to run in correct dirs
+
+## v2.5.5
+- Added config for Machine Name and option to add to Notifications
+- Added option to include Job ID to notification title
+- Added JSON notification option
+- Added option to have Child servers display on Home Screen (includes Name from above)
+- Added Flask CORS (to allow cross-domain fetching for Child server status)
+- Added Eject to Abandon
+- Added option to check for 99 Track DRM (Mostly Disney DVDs) to arm_wrapper.sh
+- Rewrote arm_wrapper.sh to eliminate duplicate tasks. #82 
+- Incorporated upstream changes to install scripts (password can be passed into script, detect latest MakeMKV version)
+- Reordered some apt options in install scripts to make it easier to cross-diff quiet/"loud" versions
+- Modified install scripts to create /mnt/dev links and fstab entries for all sr devices
+- Reloudened Debian install script
+- Tested install scripts with Debian 11 and Ubuntu 21. Minor tweaks, added red to Ubuntu
+- Cleaned up a LOT of javascript in jobRefresh.js for UI. Modernized, stricter, added child watching
+
+
+## v2.5.3
+   - Added Pagination to database and history pages
+   - Updated database page to remove old card format
+   - Added support for Android and IOS allowing better display on mobile devices
+   - Refactored a lot to make things easier to read, large changes to main.py, utils.py, etc
+   - DEBUG mode is now the default in the v2_devel branch
+   - Re-added ubuntu-quicksync.sh to allow quick install of HW acceleration support
+   - Added Update admin password option
+   - Bugfix (CD's not ripping)
+   - Bugfix (changeparams not showing correct information)
+   - Bugfix (arm_wrapper.sh was not executable)
+   - Bugfix (remove TMDB_API_KEY and ARM_API_KEY from logging)
+
+## v2.5.2
+   - Improved ajax requests for jobs on front page
+   - Abandon job now kills the PID (no files are removed)
+   - Added chown to ARMui (Fix permissions button)
+   - Bypass for forgotten password (WIP)
+   - Bugfix (arm_wrapper.sh was not executable)
+   - Bugfix (AttributeError when getting failed/successful jobs)
+   - Bugfix (sometimes there is no date in a release from mb)
+
+## v2.5.0
+  - Only one large item for this version.
+
+    Now added the possibility for users to use [TMDB](https://developers.themoviedb.org/3/getting-started/introduction) as their metadata provider, this only works for movies at the moment. 
+    In time this will have the same functionality as OMDB (movies and tv shows)
+    The idea driving this is that users should be able to choose their metadata provider.
+    I also think this is safer route in the long term, its better to have multiple options than only focus on one provider.
+    
+    - Added method to let users send/submit their correctly identified movies to a new crc64 API (an api key required)
+    - Added check for crc64 from remote database 
+
+## v2.4.6
+ - Updated jquery tablesorter, old version was vulnerable to XSS 
+ - Removed all unused versions of CSS 
+ - Smalls validation checks when searching the database page. (searching now requires min 3 chars)
+ - Small changes to index.html (home for arm ui) to warn before abandoning jobs
+ - Jquery ui now fully removed. Now uses only bootstrap for theming
+ - ARM ui database no longer needs logfiles in url (potentially dangerous), it checks the database instead for the logfile matching the job.
+ - Some progress on converting all string types to fstrings where possible
+ - ARM will now break out of wait if the user inputs/searches for movie/series.
+
+## v2.3.4 - v2.4.5
+ - Adding bypass for db.session.commit() error for movies (WIP only MakeMKV and part of handbrake is coded)
+ - Abandon job option added to main ARM ui page (for now this only sets job to failed no processes are cancelled)
+ - Typo fixes (ARM ui images has/had some typos these have been updated and corrected)
+ - ARM ui now shows CPU temps
+ - ARM ui now uses percentage bars to more clearly display storage and RAM usage 
+ - ARM ui database page is now fully functional with updated ui that looks clearer and with more details
+ - ARM ui database is now searchable
+ - ARM ui settings page now fully works and saves your settings to the arm.yaml
+ - ARM ui now prevents logfiles that contain "../"
+ - ARM ui login page updated to look smoother look
+ - Bugfix (ARM will no longer log failures when opening sdx or hdx devices)
+ - Bugfix (ARM will no longer crash when dealing with non utf-8 chars)
+ - Bugfix (ARM database_updater() was setting incorrect values into the database)
+ - Bugfix (ARM ui will no longer crash when trying to read logs with non utf-8 chars)
+ - Bugfix (ARM ui will now get the latest % of encode, this was buggy as it was getting the very first % it could find)
+ - Bugfix (ARM ui will now correctly display ram usage)
+ - Bugfix (ARM ui now correctly deals with setup (it should now create all necessary folders and do so without errors) )
+ - Bugfix (ARM ui update title no longer shows html on update)
+
+## v2.3.4
+ - Travisci/flake8 code fixes
+ - github actions added
+ - Bugfix(small bugfix for datadiscs)
+ - Bugfix (old versions of yaml would cause Exceptions)
+ - Bugfix (db connections are now closed properly for CD's)
+ - added bypass for music CD's erroring when trying to commit to the db at the same time
+
+## v2.3.3
+
+ - A smaller more manageable update this time 
+ - Early changes for cleaner looking log output
+  - Security (HandBrake.py outputs the new prettytable format)
+  - Bugfix (Transcode limit is now respected) 
+  - Bugfix (Bluray disc with no titles will now be handled correctly and will not throw an exception )
+  - Bugfix (abcde.config now correctly uses musicbrainz)
+
+## v2.3.2
+ - Added prettytables for logging
+ - Remove api/keys from the Config class string printout 
+  - Security (HandBrake.py was still outputting all api key and secrets to log file. This has now been fixed)
+  - Bugfix (Transcode limit is now respected) 
+  - Bugfix (Bluray disc with no titles will now be handled correctly and will not throw an exception ) 
+
+## v2.2.0
+ - Added Apprise notifications
+  - Added more to the Basic web framework (flask_login)
+    - Added login/admin account
+    - Added dynamic webserver ip to notifications
+    - Allow Deleting entries from the db (also warning for both the page and every delete)
+    - Added music CD covers (provided by musicbrainz & coverartarchive.org)
+    - Added CPU/RAM info on index page
+    - Added some clearer display for the listlogs page 
+    - Bugfix (Mainfeature now works when updating in the ui) 
+    - Bugfix (Job is no longer added twice when updated in ui) 
+    - ALPHA: Added ARM settings page (This only shows settings for the moment, no editing)
+  - Added Intel QuickSync Video support
+  - Added AMD VCE support
+  - Added desktop notifications
+  - Added user table to the sqlite db
+  - Added Debian Installer Script
+  - Added Ubuntu Installer Script
+  - Added Auto Identify of music CD's
+  - Made changes to the setup logging to allow music CD's to use the their artist name and album name as the log file 
+  - Added abcde config file override (This lets you give a custom config file to abcde from anywhere)
+  - Added log cleaner function to strip out secret keys (This isn't complete yet)
+  - Bugfix (datadiscs with no label no longer fail) 
+  - Bugfix (NONE_(timestamp).log will no longer be generated ) 
+
+## v2.1.0
+ - Added new package (armui) for web user interface
+  - Basic web framework (Flask, Bootstrap)
+    - Retitle functionality
+    - View or download logs of active and past rips
+  - sqlite db
+
+## v2.0.1
+ - Fixed crash inserting bluray when bdmt_eng.xml file is not present
+ - Fixed error when deleting non-existent raw files
+ - Fixed file extension config parameter not being honored when RIPMETHOD='mkv'
+ - Fixed media not being moved when skip_transcode=True
+ - Added logic for when skip_trancode=True to make it consistent with standard processing
+ - Removed systemd and reimplemented arm_wrapper.sh (see Readme for upgrade instructions)
+
+## v2.0.0
+ - Rewritten completely in Python
+ - Run as non-root
+ - Separate HandBrake arguments and profiles for DVD's and Bluray's
+ - Set video type or automatically identify
+ - Better logging
+-  Auto download latest keys_hashed.txt and KEYDB.cfg
+
+## v1.3.0
+ - Get Title for DVD and Blu-Rays so that media servers can identify them easily.
+ - Determine if video is Movie or TV-Show from OMDB API query so that different actions can be taken (TV shows usually require manual episode identification)
+ - Option for MakeMKV to rip using backup method.
+ - Option to rip only main feature if so desired.
+
+## v1.2.0
+- Distinguish UDF data from UDF video discs
+
+## v1.1.1
+
+- Added devname to abcde command
+- Added logging stats (timers). "grep STAT" to see parse them out.
+
+## v1.1.0
+
+- Added ability to rip from multiple drives at the same time
+- Added a config file for parameters
+- Changed logging
+  - Log name is based on ID_FS_LABEL (dvd name) variable set by udev in order to isolate logging from multiple process running simultaneously
+  - Log file name and path set in config file
+  - Log file cleanup based on parameter set in config file
+- Added phone notification options for Pushbullet and IFTTT
+- Remove MakeMKV destination directory after HandBrake finishes transcoding
+- Misc stuff
+
+## v1.0.1
+
+- Fix ripping "Audio CDs" in ISO9660 format like LOTR.
+
+## v1.0.0
+
+- Initial Release
diff --git a/arm_wiki/Configuring-ARM.md b/arm_wiki/Configuring-ARM.md
new file mode 100644
index 000000000..b08a3ad7a
--- /dev/null
+++ b/arm_wiki/Configuring-ARM.md
@@ -0,0 +1,46 @@
+## Configure ARM
+
+- Edit your "config" file (located at /opt/arm/arm.yaml) to determine what options you'd like to use.  Pay special attention to the 'directory setup' section and make sure the 'arm' user has write access to wherever you define these directories.
+
+- Edit the music config file (located at /home/arm/.abcde.conf)
+
+- To rip Blu-Rays after the MakeMKV trial is up you will need to purchase a license key or while MakeMKV is in BETA you can get a free key (which you will need to update from time to time) here:  https://www.makemkv.com/forum2/viewtopic.php?f=5&t=1053 and create /home/arm/.MakeMKV/settings.conf with the contents:
+
+        app_Key = "insertlicensekeyhere"
+
+- For ARM to identify movie/tv titles register for an API key at OMDb API: http://www.omdbapi.com/apikey.aspx and set the OMDB_API_KEY parameter in the config file.
+
+
+**Email notifcations**
+
+A lot of random problems are found in the sysmail, email alerting is a most effective method for debugging and monitoring.
+
+I recommend you install postfix from here:http://mhawthorne.net/posts/2011-postfix-configuring-gmail-as-relay/
+
+Then configure /etc/aliases 
+	e.g.: 
+	
+	```	
+	root: my_email@gmail.com
+	arm: my_email@gmail.com
+	userAccount: my_email@gmail.com
+	```
+	
+Run below to pick up the aliases
+
+	```
+	sudo newaliases
+	```
+## Apprise notifications
+
+You can enable Apprise notifications by editing your arm.yaml file. 
+You will need to find
+ 
+`APPRISE: ""`
+
+Then add your apprise.yaml file to here like so.
+
+`APPRISE: "/opt/arm/apprise.yaml"`
+
+A sample apprise has been included with arm but is not enabled by default, you can find this file in the doc folder of your arm installation.
+You can find how to get the keys/setting up the apprise.yaml from here https://github.com/caronc/apprise/wiki
\ No newline at end of file
diff --git a/arm_wiki/Contribute.md b/arm_wiki/Contribute.md
new file mode 100644
index 000000000..c0bf82d98
--- /dev/null
+++ b/arm_wiki/Contribute.md
@@ -0,0 +1,93 @@
+# Contributing Guide
+## Introduction
+Thank you for contributing to the Automatic Ripping Machine.
+
+## Issues, Bugs, and Feature Requests
+If you find a bug, please delete the existing log for that rip, change the log level to DEBUG in your arm.yaml file and then run the rip again to get a clean log for analysis.  You can drag and drop the log onto an issue comment to attach it to the issue.
+
+Also, since ARM relies on software such a HandBrake and MakeMKV try running those programs manually to see if it's an issue there.  If you run ARM in DEBUG mode you should
+be able to see the exact call out to each program.
+
+When submitting a bug, enhancement, or feature request please indicate if you are able/willing to make the changes yourself in a pull request.
+
+## Pull Requests
+**Please submit pull request for bug fixes/features against the v2_devel branch.**
+
+To make a pull request fork this project into your own github repository and after making changes create a PR.  Read https://help.github.com/articles/creating-a-pull-request/
+
+Test your changes locally to the best of your ability to make sure nothing broke.
+
+If you are making multiple changes, please create  separate pull requests so they can be evaluated and approved individually (obviously if changes are trivial, or multiple changes are dependent on each other then one PR is fine).
+
+Update the README file in your PR if your changes require them.
+
+After submitting your PR check that the Travis CI build passes, if it doesn't you can fix those issues with additional commits.
+
+## Hardware/OS Documentation
+The installation guide is for Ubuntu20.04/Debian Buster/OMVault(debian) and the devs run it in VMware, however, many are running ARM in different environments.  If you have successfully set ARM up in a different environment and would like to assist others, please submit a howto to the [wiki](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki).   
+
+## Testing, Quality, etc.
+ 
+ ARM is written to meed the Python style guide PEP8 (https://pep8.org/). On submitting a new PR to ARM, the new and modified code will be checked against PEP8 for compliance. Prior to loading up a new PR, it is recommended that the each new or modified file within the PR be run through PEP8 (now pycodestyle).
+ ### Setting up pycodestyle
+ 
+ You can install, upgrade, and uninstall pycodestyle.py with these commands:
+ 
+ ```
+ $ pip install pycodestyle
+ $ pip install --upgrade pycodestyle
+ $ pip uninstall pycodestyle
+ ```
+ 
+ There’s also a package for Debian/Ubuntu, but it’s not always the latest version.
+ 
+ Example usage and output
+ 
+ ```
+ $ pycodestyle --first optparse.py
+ optparse.py:69:11: E401 multiple imports on one line
+ optparse.py:77:1: E302 expected 2 blank lines, found 1
+ optparse.py:88:5: E301 expected 1 blank line, found 0
+ optparse.py:222:34: W602 deprecated form of raising exception
+ optparse.py:347:31: E211 whitespace before '('
+ optparse.py:357:17: E201 whitespace after '{'
+ optparse.py:472:29: E221 multiple spaces before operator
+ optparse.py:544:21: W601 .has_key() is deprecated, use 'in'
+ ```
+ 
+ You can also make pycodestyle.py show the source code for each error, and even the relevant text from PEP 8:
+ 
+ ```
+ $ pycodestyle --show-source --show-pep8 testsuite/E40.py
+ testsuite/E40.py:2:10: E401 multiple imports on one line
+ import os, sys
+          ^
+     Imports should usually be on separate lines.
+ 
+     Okay: import os\nimport sys
+     E401: import sys, os
+ ```
+ 
+ Or you can display how often each error was found:
+ 
+ ```
+ $ pycodestyle --statistics -qq Python-2.5/Lib
+ 232     E201 whitespace after '['
+ 599     E202 whitespace before ')'
+ 631     E203 whitespace before ','
+ 842     E211 whitespace before '('
+ 2531    E221 multiple spaces before operator
+ 4473    E301 expected 1 blank line, found 0
+ 4006    E302 expected 2 blank lines, found 1
+ 165     E303 too many blank lines (4)
+ 325     E401 multiple imports on one line
+ 3615    E501 line too long (82 characters)
+ 612     W601 .has_key() is deprecated, use 'in'
+ 1188    W602 deprecated form of raising exception
+ ```
+ 
+ Source: https://pypi.org/project/pycodestyle/
+ 
+### Testing out ARM
+ 
+ If you are interested in helping out with testing, quality, etc. please let us know.
diff --git a/arm_wiki/Contributing-Guide.md b/arm_wiki/Contributing-Guide.md
new file mode 100644
index 000000000..b13f04ec8
--- /dev/null
+++ b/arm_wiki/Contributing-Guide.md
@@ -0,0 +1,32 @@
+# Contributing Guide
+## Introduction
+Thank you for contributing to the Automatic Ripping Machine.
+
+## Issues, Bugs, and Feature Requests
+If you find a bug, please delete the existing log for that rip, change the log level to DEBUG in your arm.yaml file and then run the rip again to get a clean log for analysis.  You can drag and drop the log onto an issue comment to attach it to the issue.
+
+Also, since ARM relies on software such a HandBrake and MakeMKV try running those programs manually to see if it's an issue there.  If you run ARM in DEBUG mode you should
+be able to see the exact call out to each program.
+
+When submitting a bug, enhancement, or feature request please indicate if you are able/willing to make the changes yourself in a pull request.
+
+## Pull Requests
+Please submit pull request for bug fixes against the v2_fixes branch and features against the v2.x_dev branch.
+
+To make a pull request fork this project into your own github repository and after making changes create a PR.  Read https://help.github.com/articles/creating-a-pull-request/
+
+Test your changes locally to the best of your ability to make sure nothing broke.
+
+If you are making multiple changes, please create  separate pull requests so they can be evaluated and approved individually (obviously if changes are trivial, or multiple changes are dependent on each other then one PR is fine).
+
+Update the README file in your PR if your changes require them.
+
+After submitting your PR check that the Travis CI build passes, if it doesn't you can fix those issues with additional commits.
+
+## Hardware/OS Documentation
+The installation guide is for Ubuntu18.04 and the devs run it in VMware, however, many are running ARM in different environments.  If you have successfully set ARM up in a different environment and would like to assist others, please submit a howto to the [wiki](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki).   
+
+## Testing, Quality, etc.
+If you are interested in helping out with testing, quality, etc. please let us know.
+
+
diff --git a/arm_wiki/Docker-Dev-quickstart.md b/arm_wiki/Docker-Dev-quickstart.md
new file mode 100644
index 000000000..1222d33ea
--- /dev/null
+++ b/arm_wiki/Docker-Dev-quickstart.md
@@ -0,0 +1,80 @@
+# Setup guide for Developing an ARM docker image
+
+1. The first step is to make you sure have docker installed (either locally or over a network)
+
+2. Choose your preferred IDE (Notepad++ can work or even IDLE, but a full IDE with all the extras will make things much easier)
+    - PyCharm (CE is free) 
+    - Visual Studio
+    - Atom
+    - etc, etc
+3. Install the docker plugin for your IDE (You can skip this step if you IDE comes with Dockerfile support)
+
+4. Clone the docker branch to your filesystem
+    - `git clone --recurse-submodule https://github.com/1337-server/automatic-ripping-machine.git` (This will clone to the current directory)
+
+5. Open the cloned directory with your IDE
+
+**From this point on i assume that you are using PyCharm, The IDE's all vary in how they deploy/build the docker image. And i prefer PyCharm so I'll explain the steps for it, in hopes that this might apply to other IDE's.**
+
+6. With the project folder open
+    - Open the Dockerfile Look for the line `FROM ubuntu:20.04 as base`
+    - If you can see 2 green arrows `>>` in the gutter (beside the line numbers), You can click it to run/build the docker image.
+    - This will build with all default settings. This might work depending on your setup
+    - If not continue to next step
+
+7. Add/connect your docker server
+    - File -> Settings - > Build, Execution, Deployment -> Docker
+    - Click the + icon
+    - Name can be anything
+    - If your docker is on the same machine You can use the Unix socket default
+    - If you're working over a network you will need to provide the link to either the docker executable or your docker api url
+    - Pycharm will tell you if the connection was successful or not.
+    - Apply/Ok
+
+8. Add a Run/Debug configuration
+    - run-> Edit Configurations
+    - The + icon to add a new configuration 
+    - Select Docker->'Dockerfile'
+    - Name: Can be anything
+    - Server: This can vary depending on your use case (Use the server you setup from the previous step)
+    - Build
+      - Dockerfile: Select the Dockerfile using the built in Browser or enter the path to the Dockerfile
+      - Image tag: `1337-server/automatic-ripping-machine` (Your preference if you change this)
+    - Run
+      - Click [Modify]() and enable/tick
+        - Run built image
+        - Bind ports
+        - Bind mounts
+        - Environment Variables
+        - Run Options
+      - Container Name: arm-rippers
+      - Bind ports 
+        - `8080:8080`
+      - Bind mounts (Each folder/-v needs to be added as with the docker run command)
+        - `/home/arm:/home/arm`
+        - `/home/arm/config:/home/arm/config`  
+        - `/home/arm/Music:/home/arm/Music`  
+        - `/home/arm/logs:/home/arm/logs`
+        - `/home/arm/media:/home/arm/media`
+
+      - Environment Variables (Change these as needed)
+        - `MAKEMKV_APP_KEY=keygoeshere` 
+        - `UID=1000`
+        - `GID=1000` 
+        - `PYTHONUNBUFFERED=0`
+      - Run Options
+        - `--privileged`
+9. Save the Run config
+
+10. Once you have made changes you should now be able to Run/build the image (Shift+F10).
+   It should now build the image, push the image to docker and then open a new tab in Pycharm labeled Services. 
+   This will output the dockers log for easier debugging.
+
+# Troubleshooting
+
+### `[Errno 2] No such file or directory: 'curl-config'` when installing python requirements
+This issue is caused by your system not having the `curl` libraries installed.  
+To fix this on Ubuntu or Debian, run:
+```bash
+sudo apt install libcurl4-openssl-dev libssl-dev
+```
\ No newline at end of file
diff --git a/arm_wiki/Docker-Troubleshooting.md b/arm_wiki/Docker-Troubleshooting.md
new file mode 100644
index 000000000..7f0337a61
--- /dev/null
+++ b/arm_wiki/Docker-Troubleshooting.md
@@ -0,0 +1,52 @@
+
+# Troubleshooting
+
+## Nothing happens when i insert a disc
+
+For me personally i had to add the `--privileged` flag to my container for it to fully work, However i'm very new to docker there may be a better work around to get it to work. But this is how i got it working.
+
+You can check if your udev rules are working on the host machine via linux logs 
+
+`tail -f /var/log/syslog | grep ARM`
+
+This should show when you insert a disc
+```
+xxx ARM: container 'arm-rippers' status: "Up 24 seconds"
+xxx ARM: Starting rip
+```
+If it doesnt you udev isnt setup on the host machine.
+
+## MakeMKV cant find drives
+MakeMKV requires both drive identifiers to be passed into the container for example if `lsscsi -g` outputs
+
+`cd/dvd  TEAC     DVD-ROM DV28SV   R.0C  /dev/sr0   /dev/sg5 `
+
+You will need to add 
+```
+--device /dev/sr0
+--device /dev/sg5
+```
+to the docker run command
+
+Failing to do so may mean that the rest of ARM can find the drive but MakeMKV fails as it uses  SCSI commands to interact with the drive
+
+## Docker is adding jobs but no files are created
+Check the docker to make sure both the UID and GID match to a user outside the container, and the user has write permissions to the media directory.
+You may need to chmod your media/music directories outside the container. 
+
+## Changing where the docker puts files
+**DO NOT try to change these paths in the arm.yaml** 
+
+Instead change the containers volume paths. 
+These can be changed to suit your needs
+```
+    -v "/my-music-path:/home/arm/Music" \
+    -v "/my-config-path:/home/arm/config" \
+    -v "/my-logs-path:/home/arm/logs" \
+    -v "/my-media-path:/home/arm/media" \
+```
+
+## NVENC doesn't work
+
+Be sure that both variables for `NVIDIA_DRIVER_CAPABILITIES=all`
+and `--gpus all` are set as NVENC won't work without them
\ No newline at end of file
diff --git a/arm_wiki/FAQ.md b/arm_wiki/FAQ.md
new file mode 100644
index 000000000..21efd9f68
--- /dev/null
+++ b/arm_wiki/FAQ.md
@@ -0,0 +1,105 @@
+# Frequently asked questions
+
+## My arm wont start when i insert a disc ?
+
+When a disc is inserted, udev rules should launch a script (scripts/arm_wrapper.sh) that will launch ARM.  Here are some basic troubleshooting steps:
+- Look for empty.log.  
+  - Everytime you eject the cdrom, an entry should be entered in empty.log like:
+  ```
+  [2018-08-05 11:39:45] INFO ARM: main.<module> Drive appears to be empty or is not ready.  Exiting ARM.
+  ```
+  - Empty.log should be in your logs directory as defined in your arm.yaml file.  If there is no empty.log file, or entries are not being entered when you eject the cdrom drive, then udev is not launching ARM correctly.  Check the instructions and make sure the symlink to 51-automedia.rules is set up right.  I've you've changed the link or the file contents you need to reload your udev rules with:
+  ```
+  sudo udevadm control --reload-rules 
+  ```
+- Make sure the user arm has write permission to the location you have set in your arm.yaml
+    You can test these permissions by inserting a disc and running (remember to replace sr0 with the name of your own device)
+	
+    `sudo -u arm /usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0`
+
+- Check that  the arm_wrapper.sh is executable
+  try running `tail -f /var/log/syslog` before you insert a disc, then watch for
+
+  `sr0: Process '/opt/arm/scripts/arm_wrapper.sh sr0' failed with exit code 1`
+
+  If you see this in your logs it can mean arm_wrapper.sh isn't executable, you can fix this by running
+   
+  `sudo chmod +x /opt/arm/scripts/arm_wrapper.sh`
+
+- Lastly is to check the output of `tail -f /var/log/syslog`
+  ARM may be starting, erroring out and then sending an email before it exits. Check the arm user email for any status messages. You can use the command line 'mail' command to read these. Its rudimentary but it will give any error messages stopping ARM from running.
+
+## Is there a way to disable HandBrake encoding, I just want to rip the whole feature leaving it a .mkv file.
+
+You can either edit the arm.yaml manually with: `sudo nano /opt/arm/arm.yaml` or you can use the ARM settings page to update
+
+`SKIP_TRANSCODE: false`
+
+Change false to true
+
+`Save the changes to arm.yaml (Ctr + S  then Ctr + x) or pressing submit on the ARM settings page
+
+## ARM won't eject the DVD until it finishes transcoding
+
+To enable stacking of DVD's there are a couple of settings that must be changed
+ - `RIPMETHOD: "mkv"` and `MAINFEATURE: false`
+ - Rip method being set to mkv tells arm to use MakeMKV to pull the contents to disk(the raw folder), by default arm will try to transcode straight from the disc
+ - Main feature being turned off tells arm that it wants everthing from the disc and not just the main feature.
+
+The reason these aren't enabled by default is that Rip method being set to mkv can cause issues with blurays
+
+## I can't get Intel QuickSync to work
+
+- To check if **Intel QuickSync** is enabled and is set up correctly you can run
+   ```
+    HandBrakeCLI --help | grep -A12 "Select video encoder"
+   ```
+  You should see some entries with
+  ```
+  qsv_265
+  qsv_264
+  ```
+ If none of these are showing, you need to install Intel Media SDK [MediaSDK](https://github.com/Intel-Media-SDK/MediaSDK) and its requirements & install the correct driver for your graphics. **You also may need to recompile HandBrake from source depending on your distro**
+
+- If they are showing are you using the correct profile ? For QSV there are 2 built in profiles you can use 
+
+  - `H.265 QSV 2160p 4K`
+  - `H.265 QSV 1080p`
+
+- You can use HandBrakeCLI -z to show all the profiles available
+
+## I cant get AMD VCE to work
+
+- To check if **AMD VCE** is enabled and is set up correctly you can run
+   ```
+    HandBrakeCLI --help | grep -A12 "Select video encoder"
+   ```
+  You should see some entries with
+  ```
+  vce_h264
+  vce_h265
+  ```
+ If none of these are showing, you need to install the amdgpu-pro drivers & amf-amdgpu-pro package. You will also need to install the Vulkan SDK. 
+
+- If they are showing are you using the correct profile ? For VCE there is only 1 built in profiles you can use 
+  - `H.264 VCE 1080p`
+
+- Make sure you only install drivers for your own graphics card. Installing incorrect drivers can cause issues with AMD VCE (personally mesa-vulkan-drivers caused a headache, your own may vary)
+
+- Did you compile HandBrakeCLI from source ? Currently, VCE in not enabled by default by any distro. To enable VCE you **MUST** Compile HandBrake from source with the `--enable-vce` flag set. You can see an example of the code [HERE](https://github.com/1337-server/automatic-ripping-machine/blob/v2.2_dev_ubuntu/scripts/ubuntu-quicksync.sh)
+
+
+## I cant get NVIDIA NVENC to work
+ - I have no idea, and I can't test.
+
+## Other problems
+- Check ARM log files 
+  - The default location is /home/arm/logs/ (unless this is changed in your arm.yaml file) and is named after the dvd. These are very verbose.  You can filter them a little by piping the log through grep.  Something like 
+  ```
+  cat <logname> | grep ARM:
+  ```  
+    This will filter out the MakeMKV and HandBrake entries and only output the ARM log entries.
+  - You can change the verbosity in the arm.yaml file.  DEBUG will give you more information about what ARM is trying to do.  Note: please run a rip in DEBUG mode if you want to post to an issue for assistance.  
+  - Ideally, if you are going to post a log for help, please delete the log file, and re-run the disc in DEBUG mode.  This ensures we get the most information possible and don't have to parse the file for multiple rips.
+
+If you need any help feel free to open an issue.  Please see the above note about posting a log.
diff --git a/arm_wiki/General-Troubleshooting.md b/arm_wiki/General-Troubleshooting.md
new file mode 100644
index 000000000..d3ea04af1
--- /dev/null
+++ b/arm_wiki/General-Troubleshooting.md
@@ -0,0 +1,70 @@
+# Troubleshooting
+
+## My arm won't start when I insert a disc ?
+
+When a disc is inserted, udev rules should launch a script (scripts/arm_wrapper.sh) that will launch ARM.  Here are some basic troubleshooting steps:
+- Look for empty.log.  
+  - Every time you eject the CD-ROM, an entry should be entered in empty.log like:
+  ```
+  [2018-08-05 11:39:45] INFO ARM: main.<module> Drive appears to be empty or is not ready.  Exiting ARM.
+  ```
+  - Empty.log should be in your logs directory, as defined in your arm.yaml file.  If there is no empty.log file, or entries are not being entered when you eject the CD-ROM drive, then udev is not launching ARM correctly.  Check the instructions and make sure the symlink to 51-automedia.rules is set up right.  I've you've changed the link or the file contents you need to reload your udev rules with:
+  ```
+  sudo udevadm control --reload-rules 
+  ```
+- Make sure the user arm has write permission to the locations you have set in your arm.yaml
+    You can test these permissions by inserting a disc and running (remember to replace sr0 with the name of your own device)
+	
+    `sudo -u arm /usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0`
+
+- Make sure the db file and folder is writeable by the arm user.
+
+    The default location is `/home/arm/db/`
+
+## Other problems
+- Check ARM log files 
+  - The default location is /home/arm/logs/ (unless this is changed in your arm.yaml file) and is named after the dvd. These are very verbose.  You can filter them a little by piping the log through grep.  Something like
+  ```
+  cat /home/arm/logs/John_Wick.log | grep ARM:
+  ```  
+    This will filter out the MakeMKV and HandBrake entries and only output the ARM log entries.
+  - You can change the verbosity in the arm.yaml file.  DEBUG will give you more information about what ARM is trying to do.  Note: please run a rip in DEBUG mode if you want to post to an issue for assistance.  
+  - Ideally, if you are going to post a log for help, please delete the log file, and re-run the disc in DEBUG mode.  This ensures we get the most information possible and don't have to parse the file for multiple rips.
+
+- If you have no logs, try running `sudo -u arm /usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0` from a terminal/ssh sometimes this gives information that can't be put into a log (Python coding errors, etc)
+
+If you need any help feel free to open an issue.  Please see the wiki about posting a DEBUG log.
+
+## Changing logging to DEBUG mode
+  - Debugging mode is not enabled by default, but it offers a lot more information. If you're experiencing problems the first thing you should do is change logging to DEBUG
+
+  - You can enable Debugging by changing `LOGLEVEL` in your [arm.yaml](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/arm.yaml) to `LOGLEVEL: "DEBUG"`
+
+  - This gives a lot more information to help track down any problems.
+
+## Email notifications
+
+A lot of random problems are found in the sysmail, email alerting is a most effective method for debugging and monitoring.
+
+I recommend you install postfix from here:http://mhawthorne.net/posts/2011-postfix-configuring-gmail-as-relay/
+
+Then configure /etc/aliases e.g.:
+
+```	
+root: my_email@gmail.com
+arm: my_email@gmail.com
+userAccount: my_email@gmail.com
+```
+
+Run below to pick up the aliases
+
+```
+sudo newaliases
+```
+
+## UDF support - For users who built their own kernel
+
+If you have built your own kernel, you must add UDF support when compiling or ARM will fail to work.
+
+
+### If you think you have experienced a new bug, please open an issue.
diff --git a/arm_wiki/Getting-Started.md b/arm_wiki/Getting-Started.md
new file mode 100644
index 000000000..845b885c1
--- /dev/null
+++ b/arm_wiki/Getting-Started.md
@@ -0,0 +1,165 @@
+## Contents
+1. [Hardware Requirements](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started#Hardware-Requirements)
+2. [Installation](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started#Installation)
+3. [Docker Setup](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started#Docker-Setup)
+4. [Virtual Machine Setup](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started#Virtual-Machine-Setup)
+5. [ARM Configuration](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started#ARM-Configuration)
+6. [Additional Hardware Setup](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started#Additional-Hardware-Setup)
+
+## Hardware Requirements
+
+Operation of ARM does not require much in the way of system requirements, although it goes with out saying that a faster processor and more memory will rip media much faster. System storage is an important requirement to pay attention to, otherwise jobs will fail whilst processing if storage reaches 100%.
+- Host OS:
+   - Debian 10 (buster) ***ongoing support dropped end of 2022***
+   - Open Media Vault (5.x) ***ongoing support dropped end of 2022***
+   - Ubuntu Server 18.04 - Needs Multiverse and Universe repositories ***ongoing support dropped end of 2022***
+   - Ubuntu 20.04 - Needs Multiverse and Universe repositories
+   - **Might work with other Linux distros but this isn't tested
+- Hardware:
+   - The below are the minimum requirements to support handbrake transcoding of video files, one of the most intensive part of ARM - [Handbrake requirements](https://handbrake.fr/docs/en/latest/technical/system-requirements.html).
+   - Processor:
+      - AMD Ryzen, Threadripper, or Epyc
+      - Intel Core (6th generation and newer) i3, i5, i7, i9, or equivalent Xeon
+   - Free memory:
+      - Depends on settings used but as a general guide:
+      - 1 GB for transcoding standard definition video (480p/576p)
+      - 2 to 8 GB for transcoding high definition video (720p/1080p)
+      - 6 to 16 GB or more for transcoding ultra high definition video (2160p 4K)
+   - One or more optical drives to rip Blu-Rays, DVDs, and CDs
+- Storage:
+   - ARM Docker container 2-4 GB
+   - Audio CD: <1GB per CD ripped
+   - ARM transcode and completed folders: 10 GB or more recommended for processing and storing your new videos
+   - Blurays: requires a minimum of 10-20 GB free space to complete a rip
+- Some free time to set everything up
+
+
+## Installation
+
+ARM can be installed in multiple ways:
+- Docker install on a bare metal server/PC
+- Docker install in a VM, on a bare metal server/PC
+- On a bare metal server/PC ***Note not prefered option***
+
+### Docker Setup
+
+ARM has a prebuilt docker image ready to go with minimal steps required to start, this is the best option for new users of ARM as it requires less setup and configuration - [prebuilt image](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker).
+
+The alternative is to build the docker image from the ARM dockerfile on your system and
+       - [Build from Dockerfile](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Building-ARM-docker-image-from-source)
+
+### Virtual Machine Setup
+
+Prior to installing ARM within a virtual machine, the VM needs any hardware passed through from the host to the VM such that drive can then be passed through to docker. With multiple layers of obstraction, there is potential to not configure drives correctly which has been known to cause issues with ARM functionality and throw strange errors. Setting up the Host machine will prevent these issues from surfacing. Thanks to [stevenewbs](https://github.com/stevenewbs/blog/blob/master/libvirtd%20qemu%20Blu%20Ray%20passthrough.md) for the setup information.
+
+#### Apparmor
+
+If setup Apparmor may block access to your disk drive so you need to whitelist it.
+
+1. Check if Apparmour is blocking access:
+
+```dmesg | grep /dev/sg0``` OR ```dmesg | grep /dev/sr0```
+
+Check for "DENIED" entries for /dev/s{r,g}0
+
+2. Add lines to /etc/apparmor.d/libvirt/TEMPLATE.qemu to allow access to qemu:
+
+```
+    profile LIBVIRT_TEMPLATE flags=(attach_disconnected) {
+      #include <abstractions/libvirt-qemu>
+      /dev/sg* rwk,
+      /dev/sr* rwk,
+    }
+```
+
+3. Add the /dev... from above to /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper under the # for hostdev section:
+
+```
+    ...
+    # for hostdev
+    /dev/sr* rwk,
+    /dev/sg* rwk,
+    ...
+```
+
+4. Reload apparmor:
+
+```sudo systemctl restart apparmor```
+
+#### Libvirt / qemu config
+
+1. If it does not already exist, create the VM.
+
+2. List SCSI devices to get the ID of any CD, DVD or Bluray drives. These will be identified as an sr[0-9] drive, shown below as sr0 and sr1.
+
+```
+$ lsscsi
+[0:0:0:0]    disk    ATA      WDC WDS120G2G0A- 0000  /dev/sda
+[1:0:0:0]    cd/dvd  HL-DT-ST BDDVDRW CH12LS28 1.00  /dev/sr0
+[2:0:0:0]    disk    ATA      KINGSTON SHFS37A BBF2  /dev/sdb
+[3:0:0:0]    cd/dvd  PLDS     DVD+-RW DH-16ABS PD11  /dev/sr1
+```
+
+3. On the host, edit the VM's config.
+
+```$ sudo virsh edit <VM NAME>```
+
+4. Add a section for a SCSI controller and a new hostdev device. These need to be within the <devices> tags - the file will re-generate with your changes afterwards anyway.
+
+- The below may exist already. If not, add it.
+
+```
+  <controller type='scsi' index='0' model='virtio-scsi'>
+     <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/>
+  </controller>
+```
+
+- Following the above, add a new <hostdev> section for each drive. The adapter name needs to reflect the drive ID as provided from lssci.
+sr0 will be scsi_host1
+sr1 will be scsi_host3
+- Each hostdev entry must have a unique ID otherwise the VM won't load. In the below example sr1 is assigned unit ID of '1'.
+
+```
+  <hostdev mode='subsystem' type='scsi' managed='no'>
+    <source>
+      <adapter name='scsi_host1'/>
+      <address bus='0' target='0' unit='0'/>
+    </source>
+    <readonly/>
+    <address type='drive' controller='0' bus='0' target='0' unit='0'/>
+  </hostdev>
+  <hostdev mode='subsystem' type='scsi' managed='no'>
+    <source>
+      <adapter name='scsi_host3'/>
+      <address bus='0' target='0' unit='0'/>
+    </source>
+    <readonly/>
+    <address type='drive' controller='0' bus='0' target='0' unit='1'/>
+  </hostdev>
+```
+
+- Save and exit the editor.
+
+5. Boot the VM. Once loaded confirm with lssci that the drives have passed correctly.
+
+```
+lsscsi
+[0:0:0:0]    cd/dvd  HL-DT-ST BDDVDRW CH12LS28 1.00  /dev/sr0
+[0:0:0:1]    cd/dvd  PLDS     DVD+-RW DH-16ABS PD11  /dev/sr1
+```
+
+## ARM Configuration
+
+Once setup, ARM operates will operate with no changes to the default configuration. However, to get the most of ARM review the configuration files and modify to suit the media being ripped. See ARM [Configuration](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Configuring-ARM) for more information.
+
+
+## Additional Hardware Setup
+
+Ripping media with additional hardware configuration allows for faster transcoding and depending on the host system, should improve ripping times.
+Supported Hardware Acceleration:
+- Optional extras. None of these are required for ARM to run.
+  - For [Intel QuickSync Video support](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/intel-qsv) you need 6th Gen CPU (Skylake) or newer with QuickSync feature set
+  - For [AMD VCE support](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/amd-vce) you need RX400, 500, Vega/II, Navi series GPU or better
+  - For [NVIDIA NVENC support](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/nvidia) you need GeForce GTX Pascal (1050+) and RTX Turing (1650+, 2060+) series GPU or better
+
+**A small warning, using Intel QuickSync/AMD VCE/NVIDIA NVENC will decrease video quality, but it increases the speed of encoding significantly!**
\ No newline at end of file
diff --git a/arm_wiki/Home.md b/arm_wiki/Home.md
new file mode 100644
index 000000000..39b193f8b
--- /dev/null
+++ b/arm_wiki/Home.md
@@ -0,0 +1,43 @@
+## Overview
+
+Insert an optical disc (Blu-ray, DVD, CD) and checks to see if it's audio, video (Movie or TV), or data, then rips it.
+
+See: https://b3n.org/automatic-ripping-machine for a more detailed breakdown of how the project started.
+
+
+## Supported Operating Systems
+
+This is a small project with few maintainers. As such we do not have the time to support a large number of distributions, and system's are chosen for support by most common use. We officially support the following operating systems:
+| Operating System | Versions     |
+|------------------|--------------|
+| Ubuntu Desktop   | 20.04 |
+
+The current main development effort is going into the Docker container, for minimal issues in deployment and setup use the provided docker image.
+
+Please note that if you open an issue to ask for help, if the OS you are using is not on this list you will be asked to reimage and try again or your issue will be closed.
+
+If you use an unsupported operating system and can't or don't want to reimage, that's okay! Please try our [Docker image](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker) instead.
+
+
+## Get Started
+[Getting Started](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started on your journey with ARM
+
+## Current Features
+
+- Detects insertion of disc using udev
+- Determines disc type...
+  - If video (Blu-ray or DVD)
+    - Retrieve title from disc or OMdb API to name the folder "movie title (year)" so that Plex or Emby can pick it up
+    - Determine if video is Movie or TV using OMDb API
+    - Rip using MakeMKV or HandBrake (can rip all features or main feature)
+    - Eject disc and queue up Handbrake transcoding when done
+    - Transcoding jobs are asynchronously batched from ripping
+    - Send notifications on updates via IFTTT, Pushbullet, Pushover, Discord, Slack, Telegram and many more!
+  - If audio (CD) - rip using abcde  (get discdata and album art from musicbrainz)
+  - If data (Blu-Ray, DVD, or CD) - make an ISO backup
+- Headless, designed to be run from a server
+- Ripping from multiple-optical drives in parallel
+- HTML UI to interact with ripping jobs, view logs, etc
+- Intel QuickSync support
+- NVIDIA NVENC support
+- AMD VCE support
\ No newline at end of file
diff --git a/arm_wiki/Known-Issues.md b/arm_wiki/Known-Issues.md
new file mode 100644
index 000000000..3eaee17e3
--- /dev/null
+++ b/arm_wiki/Known-Issues.md
@@ -0,0 +1,4 @@
+The following is a list of known issues relating to ARM:
+
+* If the host running the container mid-job, any data that wasn't at rest is lost. Additionally, the job logic will be lest in a broken state and must be deleted.
+* Movies with a `/` in the name can break the rip
\ No newline at end of file
diff --git a/arm_wiki/MakeMKV-Codes.md b/arm_wiki/MakeMKV-Codes.md
new file mode 100644
index 000000000..0d1023d59
--- /dev/null
+++ b/arm_wiki/MakeMKV-Codes.md
@@ -0,0 +1,141 @@
+# Misc notes for future me / developers
+
+## TV Shows (and maybe proper movie titles)
+
+Disc info can be obtained, it returns a lot more information about each disc instead of just the 'is disc inserted'
+```makemkvcon -r info disc:[index]```
+
+## Strings returned:
+
+### Drive scan messages
+
+	DRV:index, visible, enabled, flags, drive name, disc name
+	index - drive index
+	visible - set to 1 if drive is present
+	enabled - set to 1 if drive is accessible
+	flags - media flags, see AP_DskFsFlagXXX in apdefs.h
+	drive name - drive name string
+	disc name - disc name string
+
+### Disc information output messages
+
+	TCOUT:count
+	count - titles count
+
+### Disc, title and stream information
+
+	CINFO:id,code,value
+	TINFO:id,code,value
+	SINFO:id,code,value
+
+	id - attribute id, see AP_ItemAttributeId in apdefs.h
+	code - message code if attribute value is a constant string
+	value - attribute value
+
+
+#### Example
+
+Title count
+
+	TCOUNT:7
+
+C = Disc info
+
+	CINFO:id,code,value
+	CINFO:1,6209,"Blu-ray disc" 
+	CINFO:2,0,"Breaking Bad: Season 1: Disc 1"
+	CINFO:28,0,"eng"
+	CINFO:29,0,"English"
+	CINFO:30,0,"Breaking Bad: Season 1: Disc 1"
+	CINFO:31,6119,"<b>Source information</b><br>"
+	CINFO:32,0,"BREAKINGBADS1"
+	CINFO:33,0,"0"
+
+T = Title info
+
+	TINFO:id,code,value
+	TINFO:0,2,0,"Breaking Bad: Season 1: Disc 1"
+	TINFO:0,8,0,"7"
+	TINFO:0,9,0,"0:58:06"
+	TINFO:0,10,0,"12.5 GB"
+	TINFO:0,11,0,"13472686080"
+	TINFO:0,16,0,"00763.mpls"
+	TINFO:0,25,0,"1"
+	TINFO:0,26,0,"262"
+	TINFO:0,27,0,"Breaking_Bad_Season_1_Disc_1_t00.mkv"
+	TINFO:0,28,0,"eng"
+	TINFO:0,29,0,"English"
+	TINFO:0,30,0,"Breaking Bad: Season 1: Disc 1 - 7 chapter(s) , 12.5 GB"
+	TINFO:0,31,6120,"<b>Title information</b><br>"
+	TINFO:0,33,0,"0"
+
+
+	2 - Disc Title
+	8 - Number of chapters in file
+	9 - Length of file in seconds
+	10 - File size in GB
+	11 - File size in bytes
+	27 - File name
+	28 - audio short code
+	29 - audio long code
+
+S = Details of tracks (video, audio)
+
+	SINFO:id,code,value
+	SINFO:3,0,1,6201,"Video"
+	SINFO:3,0,5,0,"V_MPEG2"
+	SINFO:3,0,6,0,"Mpeg2"
+	SINFO:3,0,7,0,"Mpeg2"
+	SINFO:3,0,13,0,"9.6 Mb/s"
+	SINFO:3,0,19,0,"720x576"
+	SINFO:3,0,20,0,"4:3"
+	SINFO:3,0,21,0,"25"
+	SINFO:3,0,22,0,"0"
+	SINFO:3,0,30,0,"Mpeg2"
+	SINFO:3,0,31,6121,"<b>Track information</b><br>"
+	SINFO:3,0,33,0,"0"
+	SINFO:3,0,38,0,""
+	SINFO:3,0,42,5088,"( Lossless conversion )"
+
+
+	20 - File Aspect ratio  #  SINFO
+	21 - File FPS  #  SINFO
+
+
+## Preferred language
+
+```CINFO``` provides title language, config this
+
+	CINFO:28,0,"eng"
+	CINFO:29,0,"English"
+
+## Subtitles
+
+	2014-07-21 22:29:18 - Filebot - DEBUG - Get [English] subtitles for 1 files
+	2014-07-21 22:29:18 - Filebot - DEBUG - Looking up subtitles by hash via OpenSubtitles
+	2014-07-21 22:29:18 - Filebot - DEBUG - Looking up subtitles by name via OpenSubtitles
+	2014-07-21 22:29:18 - Filebot - DEBUG - Fetching [Smokin'.Aces.2006.720p.BRRiP.XViD.AC3-LEGi0N.srt]
+	2014-07-21 22:29:18 - Filebot - DEBUG - Export [Smokin'.Aces.2006.720p.BRRiP.XViD.AC3-LEGi0N.srt] as: SubRip / UTF-8
+	2014-07-21 22:29:18 - Filebot - DEBUG - Writing [Smokin'.Aces.2006.720p.BRRiP.XViD.AC3-LEGi0N.srt] to [Smokin' Aces (2006).eng.srt]
+
+
+
+----------------
+
+Originally from https://github.com/JasonMillward/Autorippr/blob/master/NOTES.md
+
+
+# Info output explained
+
+When running `makemkvcon -r --cache=1 info disc:9999` each line will be a drive and its details
+
+`DRV:0,2,999,1,"DVD-ROM TEAC DVD-ROM DV28SV R.0C","WRATH_OF_THE_TITANS","/dev/sr0"`
+the line should then be split by comma and you will get this information.
+ 
+1. Drive number
+2. Drive status (empty=0, Open=1, close=2?, loading=3, not-attached=256)
+3. Unknown (Always 999)
+4. Disc type (cd=0 & null, dvd=1, BD=12,28)
+5. Drive details/name
+6. Media title/label
+7. Drive path
diff --git a/arm_wiki/Related-Projects-and-HowTos.md b/arm_wiki/Related-Projects-and-HowTos.md
new file mode 100644
index 000000000..fce392c47
--- /dev/null
+++ b/arm_wiki/Related-Projects-and-HowTos.md
@@ -0,0 +1,8 @@
+ARM under LXC / Proxmox: 
+
+https://www.reddit.com/r/homelab/comments/7bgtu9/a_simple_solution_for_getting_automated_ripping/
+
+Ansible Role:
+
+https://galaxy.ansible.com/jswetzen/automatic-ripping-machine/
+https://github.com/jswetzen/automatic-ripping-machine-setup
\ No newline at end of file
diff --git a/arm_wiki/Setting-up-(auto-install).md b/arm_wiki/Setting-up-(auto-install).md
new file mode 100644
index 000000000..32265a059
--- /dev/null
+++ b/arm_wiki/Setting-up-(auto-install).md
@@ -0,0 +1,36 @@
+## Overview
+
+There are various ways to setup ARM, the simplest would be to use the scripts inside the scrips folder. However these are not perfect and can sometimes fail.
+The best way to setup ARM for a new user is to follow along from here [Debian](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Setting-up-ARM-manually-(Debian-OMV)) or [Ubuntu](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Setting-up-ARM-manually-(Ubuntu))
+
+## Install Script For OpenMediaVault/Debian
+
+**For the attended install use:**
+ ```
+ sudo apt install wget
+ wget https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/v2_devel/scripts/debian-setup.sh
+ sudo chmod +x debian-setup.sh
+ sudo ./debian-setup.sh
+ ```
+ 
+ **For the silent install use**
+  ```
+ sudo apt -qqy install wget
+ wget https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/v2_devel/scripts/deb-install-quiet.sh
+ sudo chmod +x deb-install-quiet.sh
+ sudo ./deb-install-quiet.sh
+ ```
+
+Then ```reboot```  to complete installation.
+
+
+## Install Script For Ubuntu 20.04
+
+ ```
+sudo apt install wget
+ wget https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/v2_devel/scripts/ubuntu-20.04-install.sh
+sudo chmod +x ubuntu-20.04-install.sh
+sudo ./ubuntu-20.04-install.sh
+ ```
+
+Then ```reboot```  to complete installation.
\ No newline at end of file
diff --git a/arm_wiki/Setting-up-ARM-manually-(Debian-OMV).md b/arm_wiki/Setting-up-ARM-manually-(Debian-OMV).md
new file mode 100644
index 000000000..70d1484a7
--- /dev/null
+++ b/arm_wiki/Setting-up-ARM-manually-(Debian-OMV).md
@@ -0,0 +1,172 @@
+# IMPORTANT: This installation method is no longer supported. Please install ARM as a [Docker Container](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker) instead
+
+## Manual Installation Guide
+
+## Pre-Install (only if necessary)
+
+If you have a new DVD drive that you haven't used before, some require setting the region before they can play anything.  Be aware most DVD players only let you change the region a handful (4 or 5?) of times, then lockout any further changes.  If your region is already set, or you have a region free DVD drive, you can skip this step.
+
+```bash
+sudo apt-get install regionset
+sudo regionset /dev/sr0
+```
+
+## Install
+
+**Setup 'arm' user and Ubuntu basics:**
+
+Sets up graphics drivers, does Ubuntu update & Upgrade, gets Ubuntu to auto set up driver, and finally installs and setups up avahi-daemon
+```
+sudo groupadd arm
+sudo useradd -m arm -g arm -G cdrom
+sudo passwd arm
+echo -e "${RED}Installing git${NC}"
+sudo apt-get install git wget
+sudo apt-get install build-essential pkg-config libc6-dev libssl-dev libexpat1-dev libavcodec-dev libgl1-mesa-dev qtbase5-dev zlib1g-dev
+
+```
+
+## Set up repos and install dependencies
+
+```
+mkdir /makeMKV
+cd /makeMKV
+# see https://forum.makemkv.com/forum/viewtopic.php?f=3&t=224 for latest version number replace 1.16.7 with latest version
+wget https://www.makemkv.com/download/makemkv-bin-1.16.7.tar.gz
+wget https://www.makemkv.com/download/makemkv-oss-1.16.7.tar.gz
+
+echo -e "${RED}Extracting MakeMKV${NC}"
+tar xvzf makemkv-oss-1.16.7.tar.gz
+tar xvzf makemkv-bin-1.16.7.tar.gz
+
+cd makemkv-oss-1.16.7
+./configure
+make
+sudo make install
+
+cd ../makemkv-bin-1.16.7
+make
+sudo make install
+sudo apt install ffmpeg
+sudo apt install handbrake-cli libavcodec-extra
+sudo apt install libdvdcss2
+sudo apt install abcde flac imagemagick glyrc cdparanoia
+sudo apt install at
+sudo apt install python3 python3-pip python3-libdiscid
+sudo apt install libcurl4-openssl-dev libssl-dev  
+sudo apt install libdvd-pkg
+wget http://download.videolan.org/pub/debian/stable/libdvdcss2_1.2.13-0_amd64.deb
+wget http://download.videolan.org/pub/debian/stable/libdvdcss_1.2.13-0.debian.tar.gz
+wget http://ftp.us.debian.org/debian/pool/contrib/libd/libdvd-pkg/libdvd-pkg_1.4.0-1-2_all.deb
+sudo dpkg -i libdvdcss2_1.2.13-0_amd64.deb
+sudo dpkg -i libdvd-pkg_1.4.0-1-2_all.deb
+sudo apt --fix-broken install
+dpkg-reconfigure libdvd-pkg
+sudo apt install default-jre-headless
+sudo apt install eject
+
+```
+
+## Install and setup ARM
+
+```
+cd /opt
+mkdir arm
+chown arm:arm arm
+chmod 775 arm
+git clone https://github.com/automatic-ripping-machine/automatic-ripping-machine.git arm
+chown -R arm:arm arm
+cd arm
+pip3 install setuptools
+apt-get install python3-dev python3-pip python3-venv python3-wheel -y
+pip3 install wheel
+pip3 install -r requirements.txt 
+ln -s /opt/arm/setup/51-automedia.rules /lib/udev/rules.d/
+ln -s /opt/arm/setup/.abcde.conf /home/arm/
+cp docs/arm.yaml.sample arm.yaml
+sudo chown arm:arm arm.yaml
+mkdir /etc/arm/
+ln -s /opt/arm/arm.yaml /etc/arm/
+sudo chmod +x /opt/arm/scripts/arm_wrapper.sh
+sudo chmod +x /opt/arm/scripts/update_key.sh
+
+```
+
+## Set up drives
+
+  Create a mount point for each dvd drive.
+  If you don't know the device name, try running `dmesg | grep -i -E '\b(dvd|cd)\b'`.  The mountpoint needs to be /mnt/dev/<device name>.
+  So if your device name is `sr0`, set the mountpoint with this command:
+  ```bash
+  sudo mkdir -p /mnt/dev/sr0
+  ```
+  Repeat this for each device you plan on using with ARM.
+
+  Create entries in /etc/fstab to allow non-root to mount dvd-roms
+  Example (create for each optical drive you plan on using for ARM):
+  ```
+  /dev/sr0  /mnt/dev/sr0  udf,iso9660  users,noauto,exec,utf8  0  0
+  ```
+  OR as root
+  ```
+  echo -e "\n/dev/sr0  /mnt/dev/sr0  udf,iso9660  users,noauto,exec,utf8  0  0 \n" >> /etc/fstab
+  ```
+
+## Installing the ARMui service
+Create a new service file
+```sudo nano /etc/systemd/system/armui.service ``` 
+
+Then put this in the file
+```
+[Unit]
+Description=Arm service
+## Added to force armui to wait for network
+After=network-online.target
+Wants=network-online.target
+[Service]
+Type=simple
+User=arm
+Group=arm
+## Add your path to your logfiles if you want to enable logging
+## Remember to remove the # at the start of the line
+#StandardOutput=append:/PATH-TO-MY-LOGFILES/WebUI.log
+#StandardError=append:/PATH-TO-MY-LOGFILES/WebUI.log
+Restart=always
+RestartSec=3
+ExecStart=python3 /opt/arm/arm/runui.py
+[Install]
+WantedBy=multi-user.target
+```
+
+Now we can reload the rules and start the arm service with
+```
+sudo systemctl daemon-reload
+sudo systemctl enable armui
+sudo systemctl start armui
+```
+
+
+
+
+Setup is almost complete! Reboot...
+
+### Setting up the database
+You will need to visit your http://WEBSERVER_IP:WEBSERVER_PORT/setup  
+							&#x26A0; &#x26A0; **!!!WARNING!!!** &#x26A0; &#x26A0;  					
+
+Visiting this page will delete your current database and create a new db file. You WILL lose jobs/tracks/etc from your database
+This will setup the new database, and ask you to make an admin account. Because of the changes to the ARMui it's not possible to view/change/delete entries without logging in. 
+Due to these large number of changes to the database it's not currently possible to upgrade without creating a new database, this may change later
+but for now you will lose all previous jobs/tracks/configs.
+
+Once it has deleted the current database, it will redirect you to sign in. The default username and password is
+
+- Username: admin 
+- Password: password
+
+
+Alternatively, you can insert a disc or trigger it manually by running 
+```
+/usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0 | at now
+```
+in a terminal/ssh
\ No newline at end of file
diff --git a/arm_wiki/Setting-up-ARM-manually-(Ubuntu).md b/arm_wiki/Setting-up-ARM-manually-(Ubuntu).md
new file mode 100644
index 000000000..ee4db8e36
--- /dev/null
+++ b/arm_wiki/Setting-up-ARM-manually-(Ubuntu).md
@@ -0,0 +1,150 @@
+# IMPORTANT: This installation method is no longer supported. Please install ARM as a [Docker Container](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker) instead
+
+## Manual Install Guide
+
+## Pre-Install (only if necessary)
+
+If you have a new DVD drive that you haven't used before, some require setting the region before they can play anything.  Be aware most DVD players only let you change the region a handful (4 or 5?) of times then lockout any further changes.  If your region is already set or you have a region free DVD drive you can skip this step.
+
+```bash
+sudo apt-get install regionset
+sudo regionset /dev/sr0
+```
+
+## Install
+
+### Setup 'arm' user and ubuntu basics:
+
+Sets up graphics drivers, does Ubuntu update & Upgrade, gets Ubuntu to auto set up driver, and finally installs and setups up avahi-daemon
+```bash
+sudo apt update -y && sudo apt upgrade -y 
+***optional (was not required for me): sudo add-apt-repository ppa:graphics-drivers/ppa
+sudo apt install avahi-daemon -y && sudo systemctl restart avahi-daemon
+sudo apt install ubuntu-drivers-common -y && sudo ubuntu-drivers install 
+sudo reboot
+# Installation of drivers seems to install a full gnome desktop, and it seems to set up hibernation modes.
+# It is optional to run the below line (Hibernation may be something you want.)
+	sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
+sudo groupadd arm
+sudo useradd -m arm -g arm -G cdrom
+sudo passwd arm 
+  <enter new password>
+```
+
+### Set up repos and install dependencies
+
+```bash
+sudo apt-get install git lsdvd -y
+sudo add-apt-repository ppa:heyarje/makemkv-beta
+
+NumOnly=$(cut -f2 <<< `lsb_release -r`) && case $NumOnly in "16.04" ) sudo add-apt-repository ppa:mc3man/xerus-media;; "18.04" ) sudo add-apt-repository ppa:mc3man/bionic-prop;; "20.04" ) sudo add-apt-repository ppa:mc3man/focal6;; *) echo "error in finding release version";; esac
+
+sudo apt update -y && \
+sudo apt install makemkv-bin makemkv-oss -y && \
+sudo apt install handbrake-cli libavcodec-extra -y && \
+sudo apt install abcde flac imagemagick glyrc cdparanoia -y && \
+sudo apt install at -y && \
+sudo apt install python3 python3-pip -y && \
+sudo apt-get install libcurl4-openssl-dev libssl-dev -y && \
+sudo apt-get install libdvd-pkg -y && \
+sudo dpkg-reconfigure libdvd-pkg && \
+sudo apt install default-jre-headless -y
+```
+
+### Install and setup ARM
+
+```bash
+cd /opt
+sudo mkdir arm
+sudo chown arm:arm arm
+sudo chmod 775 arm
+sudo git clone --recurse-submodules https://github.com/automatic-ripping-machine/automatic-ripping-machine.git arm
+sudo chown -R arm:arm arm
+cd arm
+sudo pip3 install -r requirements.txt 
+sudo cp /opt/arm/setup/51-automedia.rules /etc/udev/rules.d/
+sudo cp docs/arm.yaml.sample arm.yaml
+sudo chown arm:arm arm.yaml
+sudo mkdir /etc/arm/
+sudo ln -s /opt/arm/arm.yaml /etc/arm/
+sudo chmod +x /opt/arm/scripts/arm_wrapper.sh
+sudo chmod +x /opt/arm/scripts/update_key.sh
+
+cp --no-clobber "/opt/arm/setup/.abcde.conf" "/etc/.abcde.conf"
+chown arm:arm "/etc/.abcde.conf"
+sudo mkdir -p /etc/arm/config
+su - arm -c "ln -sf /etc/.abdce.conf /etc/arm/config/abcde.conf"
+
+```
+
+### Set up drives
+
+  Create a mount point for each dvd drive.
+  If you don't know the device name, try running `dmesg | grep -i -E '\b(dvd|cd)\b'`.  The mountpoint needs to be /mnt/dev/<device name>.
+  So if your device name is `sr0`, set the mountpoint with this command:
+  ```bash
+  sudo mkdir -p /mnt/dev/sr0
+  ```
+  Repeat this for each device you plan on using with ARM.
+
+  Create entries in /etc/fstab to allow non-root to mount dvd-roms
+  Example (create for each optical drive you plan on using for ARM):
+  ```
+  /dev/sr0  /mnt/dev/sr0  udf,iso9660  users,noauto,exec,utf8  0  0
+  ```
+
+
+### Installing the ARMui service
+
+    
+Create folders required to run the ARM service
+```sudo -u arm mkdir -p /home/arm/logs```
+
+Create a new service file
+```sudo nano /etc/systemd/system/armui.service ``` 
+
+Then put this in the file
+```
+[Unit]
+Description=Arm service
+## Added to force armui to wait for network
+After=network-online.target
+Wants=network-online.target
+[Service]
+Type=simple
+User=arm
+Group=arm
+## Add your path to your logfiles if you want to enable logging
+## Remember to remove the # at the start of the line
+#StandardOutput=append:/home/arm/logs/WebUI.log
+#StandardError=append:/home/arm/logs/WebUI.log
+Restart=always
+RestartSec=3
+ExecStart=python3 /opt/arm/arm/runui.py
+[Install]
+WantedBy=multi-user.target
+```
+
+Now we can reload the rules and start the arm service with
+```
+sudo systemctl daemon-reload
+sudo systemctl enable armui
+sudo systemctl start armui
+```
+
+Setup is now almost complete! Reboot...
+
+## Post install
+You may need to fix permissions in the arm home directory
+`sudo chmod -R 775 /home/arm`
+				
+The default username and password is
+
+- Username: admin 
+- Password: password
+
+Alternatively, you can insert a disc or trigger it manually by running 
+```
+/usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0 | at now
+```
+in a terminal/ssh
\ No newline at end of file
diff --git a/arm_wiki/Setting-up-ARM-script-(Debian-OMV).md b/arm_wiki/Setting-up-ARM-script-(Debian-OMV).md
new file mode 100644
index 000000000..81a97177e
--- /dev/null
+++ b/arm_wiki/Setting-up-ARM-script-(Debian-OMV).md
@@ -0,0 +1,45 @@
+# IMPORTANT: This installation method is no longer supported. Please install ARM as a [Docker Container](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker) instead
+
+# Auto Install Script For OpenMediaVault/Debian
+
+This is **not recommended** for first time installations. This was only really intended to be used to reinstall on an environment you know works fully with ARM
+
+**contrib repositories are required!**
+
+## For the attended install use:
+ ```
+sudo apt install wget
+wget https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/v2_devel/scripts/installers/debian-install.sh
+sudo chmod +x debian-install.sh
+sudo ./debian-install.sh
+sudo chmod +x /opt/arm/scripts/update_key.sh
+ ```
+ ```reboot``` 
+ to complete installation.
+
+
+## Post install
+
+### Setting up the database
+You will need to visit your http://WEBSERVER_IP:WEBSERVER_PORT/setup  
+							&#x26A0; &#x26A0; **!!!WARNING!!!** &#x26A0; &#x26A0;  					
+
+Visiting this page will delete your current database and create a new db file. You WILL lose jobs/tracks/etc from your database
+This will set up the new database, and ask you to make an admin account. Because of the changes to the armui it's not possible to view/change/delete entries without logging in. 
+Due to these large number of changes to the database it's not currently possible to upgrade without creating a new database, this may change later
+but for now you will lose all previous jobs/tracks/configs.
+
+Once it has deleted the current database, it will redirect you to sign in. The default username and password is
+
+- Username: admin 
+- Password: password
+
+
+Alternatively, you can insert a disc or trigger it manually by running 
+`/usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0 | at now` in a terminal/ssh
+
+### File Permissions 
+
+Make sure arm has write permission to the folder you have selected in the arm.yaml. If you haven't changed the arm.yaml it will be `/home/arm`
+
+For example `sudo chmod -R 777 /home/arm` **Please check/change these, this is for example only!**
\ No newline at end of file
diff --git a/arm_wiki/Ubuntu-18.04-Service-file.md b/arm_wiki/Ubuntu-18.04-Service-file.md
new file mode 100644
index 000000000..b0ae62a83
--- /dev/null
+++ b/arm_wiki/Ubuntu-18.04-Service-file.md
@@ -0,0 +1,23 @@
+# Service file for use in Ubuntu 18.04  - Last Tested 2022-04-19
+
+
+```
+[Unit]
+Description=Arm service
+## Added to force armui to wait for network
+After=network-online.target
+Wants=network-online.target
+[Service]
+Type=simple
+User=arm
+Group=arm
+## These dont work on on 18
+StandardOutput=append:/home/arm/logs/WebUI.log
+StandardError=append:/home/arm/logs/WebUI.log
+Restart=always
+RestartSec=3
+ExecStart=/bin/sh -c 'exec /usr/bin/python3 /opt/arm/arm/runui.py >/home/arm/logs/web.log 2>/home/arm/logs/web.log'
+[Install]
+WantedBy=multi-user.target
+
+```
\ No newline at end of file
diff --git a/arm_wiki/Ubuntu-20.04-Automatic-Installation.md b/arm_wiki/Ubuntu-20.04-Automatic-Installation.md
new file mode 100644
index 000000000..d323ba94c
--- /dev/null
+++ b/arm_wiki/Ubuntu-20.04-Automatic-Installation.md
@@ -0,0 +1,52 @@
+# IMPORTANT: This installation method is no longer supported. Please install ARM as a [Docker Container](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker) instead
+
+# Automatically Install ARM on Ubuntu 20.04
+The ARM installation script supports both Ubuntu Desktop 20.04 and Ubuntu Server 20.04
+
+## Installing Ubuntu
+- Select the option to install all third-party drivers
+- Make sure the username is `arm`
+
+## Prepare Ubuntu
+If running Ubuntu in a VM, make sure all disks are available to Ubuntu via hardware passthrough in the VM Hypervisor software and confirm all drives are showing up by running `lsscsi -g`
+
+```
+sudo apt install wget lsscsi
+lsscsi -g
+wget https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/main/scripts/ubuntu-20.04-install.sh
+chmod +x ubuntu-20.04-install.sh
+```
+
+## Install ARM
+The script defaults to installing a live version of ARM, but includes a `-d` flag that can be specified to install ARM in a development environment.
+
+To install ARM LIVE: `sudo ./ubuntu-20.04-install.sh`  
+To install ARM DEV: `sudo ./ubuntu-20.04-install.sh -d`
+
+After the script finishes, Firefox should open to `http:<machine_ip>:8080/setup` and prompt the user to create an admin account. If this doesn't happen, check the installer console log for error messages.
+
+## Post Install - LIVE
+No live-specific post installation steps are needed
+
+## Post Install - DEV
+1. Open Pycharm, and accept the User Agreement.
+    1. If you want to install PyCharm Professional, run `sudo snap install pycharm-professional --classic`
+    2. Select `Projects > Open`
+    3. Open `/opt/arm`
+    4. Select "Trust Project"
+    5. When the Creating Virtual Environment popup appears, click "OK"
+2. In the Project pane, open `/arm/ripper/main.py`
+3. Scroll down to `if __name__ == "__main__":`
+    1. Right click on the green arrow and select "Modify Run Configuration..."
+    2. In Parameters, type `-d sr0`
+    3. Click "OK"
+4. Insert a disk into the drive and wait for Ubuntu to show it
+5. In the upper right hand corner, click the green button to run or the green bug to run inside PyCharm's debugger
+
+### Notes
+If you terminate a debugging run early, run `mount /dev/sr0` to make sure the disk is mounted before the next run. ARM will break if the disk is not mounted. 
+
+The default username and password is
+
+- Username: admin 
+- Password: password
diff --git a/arm_wiki/Uninstall-A.R.M.md b/arm_wiki/Uninstall-A.R.M.md
new file mode 100644
index 000000000..f215ee95d
--- /dev/null
+++ b/arm_wiki/Uninstall-A.R.M.md
@@ -0,0 +1,31 @@
+# Ubuntu uninstall 
+Save this file as **uninstall_arm.sh**
+
+```
+sudo apt-get purge git -y
+sudo add-apt-repository -r -y ppa:heyarje/makemkv-beta
+sudo add-apt-repository -r -y ppa:stebbins/handbrake-releases
+sudo add-apt-repository -r -y ppa:mc3man/xerus-media
+sudo add-apt-repository -r -y ppa:mc3man/bionic-prop
+sudo add-apt-repository -r -y ppa:mc3man/focal6
+sudo apt update -y && \
+sudo apt purge makemkv-bin makemkv-oss -y && \
+sudo apt purge handbrake-cli libavcodec-extra -y && \
+sudo apt purge abcde flac imagemagick glyrc cdparanoia -y && \
+sudo apt purge at -y && \
+sudo apt purge libcurl4-openssl-dev libssl-dev -y && \
+sudo apt purge libdvd-pkg -y && \
+sudo apt purge default-jre-headless -y
+cd /opt/arm
+sudo pip3 uninstall -y -r requirements.txt 
+cd ~
+sudo rm -R /opt/arm
+sudo rm -R /home/arm
+sudo rm -R /etc/arm/
+sudo rm -R /mnt/dev/sr0
+sudo rm /etc/systemd/system/armui.service
+sudo systemctl disable armui
+sudo systemctl daemon-reload
+```
+Run `sudo chmod +x uninstall_arm.sh` in a terminal
+Then run `sudo ./uninstall_arm.sh`
\ No newline at end of file
diff --git a/arm_wiki/Upgrading-from-previous-ARM-verions.md b/arm_wiki/Upgrading-from-previous-ARM-verions.md
new file mode 100644
index 000000000..0543832ea
--- /dev/null
+++ b/arm_wiki/Upgrading-from-previous-ARM-verions.md
@@ -0,0 +1,36 @@
+## Upgrading from v2_master to v2.2_dev
+
+If you wish to upgrade from v2_master to v2.2_dev instead of a clean install, these directions should get you there.  
+
+```bash
+cd /opt/arm
+sudo git checkout v2.2_dev
+sudo pip3 install -r requirements.txt
+```
+Backup config file and replace it with the updated config
+```bash
+mv arm.yaml arm.yaml.old
+cp docs/arm.yaml.sample arm.yaml
+```
+
+There are new config parameters so review the new arm.yaml file
+
+Make sure the 'arm' user has write permissions to the db directory (see your arm.yaml file for locaton). is writeable by the arm user.  A db will be created when you first run ARM.
+
+Make sure that your rules file is properly **copied** instead of linked:
+```
+sudo rm /usr/lib/udev/rules.d/51-automedia.rules
+sudo cp /opt/arm/setup/51-automedia.rules /etc/udev/rules.d/
+```
+Otherwise you may not get the auto-launching of ARM when a disc is inserted behavior
+on Ubuntu 20.04.
+
+Please log any issues you find.  Don't forget to run in DEBUG mode if you need to submit an issue (and log files).  Also, please note that you are running 2.2_dev in your issue.
+
+You will also need to visit your http://WEBSERVER_IP:WEBSERVER_PORT/setup  
+							&#x26A0; &#x26A0; **!!!WARNING!!!** &#x26A0; &#x26A0;  					
+
+Visiting this page will delete your current database and create a new db file. You WILL lose jobs/tracks/etc from your database
+This will setup the new database, and ask you to make an admin account. Because of the changes to the armui its not possible to view/change/delete entries without logging in. 
+Due to these large number of changes to the database its not currently possible to upgrade without creating a new database
+
diff --git a/arm_wiki/VMware.md b/arm_wiki/VMware.md
new file mode 100644
index 000000000..68838f708
--- /dev/null
+++ b/arm_wiki/VMware.md
@@ -0,0 +1,2 @@
+See Ben's original blog post...
+[https://b3n.org/automatic-ripping-machine/](https://b3n.org/automatic-ripping-machine/)
\ No newline at end of file
diff --git a/arm_wiki/_Sidebar.md b/arm_wiki/_Sidebar.md
new file mode 100644
index 000000000..82ef5688e
--- /dev/null
+++ b/arm_wiki/_Sidebar.md
@@ -0,0 +1,49 @@
+**[Home](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki)**
+
+**Getting Started**
+   - [Getting Started](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Getting-Started)
+   - **Docker**
+       - [Pull prebuilt image](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/docker)
+       - [Build from Dockerfile](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Building-ARM-docker-image-from-source)
+   - **Manual Install**
+       - [Ubuntu](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Setting-up-ARM-manually-(Ubuntu))
+       - [Debian](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Setting-up-ARM-manually-(Debian-OMV))
+       - [Open Media Vault](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Setting-up-ARM-manually-(Debian-OMV))
+   - **Automatic script install**
+       - [Open Media Vault/ Debian (Install script)](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Setting-up-ARM-script-(Debian-OMV))
+       - [Ubuntu 20.04 (install script)](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Ubuntu-20.04-Automatic-Installation)
+   - [Upgrading from old versions](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/upgrading)
+
+**[Known Issues](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Known-Issues)**
+
+**Configuration**
+   - [Configuration](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Configuring-ARM)
+   - **Configuration Files**
+      - [arm.yaml](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/arm.yaml)
+      - [apprise.yaml](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/apprise.yaml)
+      - [.abcde.conf](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/.abcde.conf)
+      - [Skins for ARM ui](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/ARM-ui-skins)
+
+**Hardware Configuration**
+   - [Adding Intel QSV Support](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/intel-qsv)
+   - [Adding AMD VCE Support](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/amd-vce)
+   - [NVIDIA NVENC support](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/nvidia)
+
+**Troubleshooting**
+   - [FAQ](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/FAQ)
+   - [General Troubleshooting](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/General-Troubleshooting)
+   - [Docker Troubleshooting](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Docker-Troubleshooting)
+   - [Open An Issue](https://github.com/automatic-ripping-machine/automatic-ripping-machine/issues/new/choose)
+
+**Contributing to ARM**
+   - [Contribute](http://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Contribute)
+   - [Docker Dev guide](http://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Docker-Dev-quickstart)
+   - [ARM Development Tools (devtools)](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/ARM-Development-Tools)
+
+**How ARM Works**
+   - [ARM workflow diagram](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/workflow-diagram)
+   - **More Info**
+      - [Related Projects and HowTos](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/related-howtos)
+      - [Hardware/OS HowTo's](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/VMware)
+      - [The ARM Change log](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/Change-Log)
+      - [The ARM License](https://github.com/automatic-ripping-machine/automatic-ripping-machine/blob/v2_devel/LICENSE)
\ No newline at end of file
diff --git a/arm_wiki/amd-vce.md b/arm_wiki/amd-vce.md
new file mode 100644
index 000000000..b71c2ae7d
--- /dev/null
+++ b/arm_wiki/amd-vce.md
@@ -0,0 +1,103 @@
+# Adding AMD VCE Support
+
+## Hardware/Software Requirements
+ - AMD Radeon RX 400, 500, Vega/II, Navi series GPU or better
+ - Ubuntu Linux 20.04 or later
+ - AMD Radeon Software for Linux version 19.20
+ - Manually install the amf-amdgpu-pro package included with the AMD drivers
+ - Vulkan SDK
+
+If you have these you can continue...
+
+
+Currently no distros enable AMD VCE by default in their packages of HandBrake/CLI. Not Even HandBrake themselves have it enabled for linux. It is considered bleeding edge and highly experimental. VCE support needs to be added manually, this means rebuilding HandBrake from source.
+
+## Ubuntu 20.04
+I have made a script that will Install all the requirements for Intel QSV & enable AMD VCE from the HandBrake build.
+**This is only tested on Ubuntu 20.04**
+You can either follow along the [commands](https://github.com/automatic-ripping-machine/automatic-ripping-machine/blob/v2_devel/scripts/ubuntu-quicksync.sh) or you can run:
+
+ ```
+ sudo apt install wget
+ wget https://github.com/automatic-ripping-machine/automatic-ripping-machine/blob/v2_devel/scripts/ubuntu-quicksync.sh 
+ sudo chmod +x ubuntu-quicksync.sh
+ sudo ./ubuntu-quicksync.sh
+ ```
+ Remember to `reboot` to complete installation.
+ 
+This script installs some additional requirements for Intel QSV, and was for Ubuntu if you would like to only enable VCE. 
+You can use these commands 
+
+``` 
+## Handbrake -  We use this one for the h.264 VCE preset
+## The HandBrake repo doesn't include and profiles for VCE h.264
+## If you dont need h.264 you can use
+###git clone https://github.com/HandBrake/HandBrake.git && cd HandBrake
+git clone https://github.com/1337-server/HandBrake.git && cd HandBrake
+./configure --disable-gtk --enable-vce --launch-jobs=$(nproc) --launch
+sudo make --directory=build install
+```
+
+But you will need to make you sure have all the dependencies for your own distro. 
+
+## Other distros/Linux version
+
+You can find full details for your own version from the Official HandBrake Documentation  [**HERE**](https://handbrake.fr/docs/en/1.3.0/developer/build-linux.html)
+You will need to install all the dependencies, then run
+
+``` 
+## Handbrake -  We use this one for the h.264 VCE preset
+## The HandBrake repo doesn't include and profiles for VCE h.264
+## If you dont need h.264 you can use
+###git clone https://github.com/HandBrake/HandBrake.git && cd HandBrake
+git clone https://github.com/HandBrake/HandBrake.git && cd HandBrake
+./configure --disable-gtk --enable-qsv --enable-vce --launch-jobs=$(nproc) --launch
+sudo make --directory=build install
+```
+
+
+## After installation
+
+`HandBrakeCLI --help | grep -A12 "Select video encoder"`
+
+If VCE is enabled should give something similar to 
+
+```
+   -e, --encoder <string>  Select video encoder:
+                               x264
+                               x264_10bit
+                               vce_h264
+                               x265
+                               x265_10bit
+                               x265_12bit
+                               vce_h265
+                               mpeg4
+                               mpeg2
+                               VP8
+                               VP9
+HandBrake has exited.
+
+```
+
+Once you see your encoder is installed correctly you can now set `H.264 VCE 1080p` as your profile in your arm.yaml config and it will use hardware encoding to speed things up.
+
+
+You will also need to add the arm user to the video & render groups so that arm can access the VCE encoder
+```
+sudo usermod -a -G video arm 
+sudo usermod -a -G render arm
+```
+
+## If you want to use the original HandBrake/HandBrake repo
+
+This means you need pull the repo and manually edit [libhb/handbrake/preset_builtin.h](https://github.com/HandBrake/HandBrake/blob/master/libhb/handbrake/preset_builtin.h)
+to add a h.264 VCE profile.
+
+If you dont need h.264 you can pull directly from https://github.com/HandBrake/HandBrake
+
+Then you can build HandBrake and use it for ARM.
+
+The full instuctions to build HandBrake for your own distro can be found here [HandBrake Docs](https://handbrake.fr/docs/en/latest/developer/build-linux.html)
+
+## HandBrake Official Documentation 
+For more detailed information you can read through the official HandBrake documentation [HandBrake Building for linux](https://handbrake.fr/docs/en/1.3.0/developer/build-linux.html)
diff --git a/arm_wiki/apprise.yaml.md b/arm_wiki/apprise.yaml.md
new file mode 100644
index 000000000..a5177edcd
--- /dev/null
+++ b/arm_wiki/apprise.yaml.md
@@ -0,0 +1,51 @@
+# The apprise.yaml config file
+
+ This is the config file for apprise notifications, it only contains settings for the apprise notifications.
+Its **strongly** advised to set at least one of these up when first setting up ARM. These notifications make solving problems much easier. 
+
+
+The default location for this file is `/opt/arm/docs/apprise.yaml`
+
+[Apprise](https://github.com/caronc/apprise/wiki) does support more methods than are listed here. 
+If you would like a services added to ARM that is not yet listed here, please open an issue or submit a pull request.
+
+**Only the services listed here have been added to ARM**. 
+
+  - LaMetric
+  - Mailgun
+  - Boxcar
+  - Discord
+  - Fast
+  - Flock
+  - Gitter
+  - Gotify
+  - Growl
+  - Join
+  - Kodi
+  - Kumulos
+  - Matrix
+  - Nextcloud
+  - Notica
+  - Notifico
+  - Office365
+  - Popcorn
+  - Prowl
+  - Pushjet
+  - Push
+  - Pushed
+  - Rocketchat
+  - Ryver 
+  - Sendgrid
+  - Simplepush
+  - Slack
+  - Spark
+  - Spontit
+  - Telegram
+  - Twist
+  - XBMC
+  - XMPP
+  - Webex teams
+  - Zilup
+
+
+You can view the full file here  [apprise.yaml](https://github.com/automatic-ripping-machine/automatic-ripping-machine/blob/v2_devel/docs/apprise.yaml)
\ No newline at end of file
diff --git a/arm_wiki/arm.yaml.md b/arm_wiki/arm.yaml.md
new file mode 100644
index 000000000..a4044219e
--- /dev/null
+++ b/arm_wiki/arm.yaml.md
@@ -0,0 +1,26 @@
+# The arm.yaml config file
+
+This is the config file for almost all changeable settings of ARM, all of these are very well documented in the file itself.  
+
+The default location for this file is `/etc/arm/config/arm.yaml`
+ 
+However for clarity they are listed here.
+
+They include 
+
+  - UDF disc check
+  - Contacting [OMdb](http://www.omdbapi.com/)/auto identify movies or series
+  - HandBrake Settings (profile, arguments, and file extention)
+  - MakeMKV settings (rip method, arguments)
+  - A manual wait time (useful for overriding the OMdb identify or disc mode)
+  - Enable or disable ripping of the same disc
+  - Media directory settings (identified, unidentified, raw disc files locations)
+  - All of the logging level settings and directory
+  - The ARM web-server ip and port
+  - Emby notification/server details (allowing emby refresh after rips)
+  - Notification settings (Pushbullet, IFTTT, Pushover)
+  - The location of your [apprise.yaml](https://github.com/automatic-ripping-machine/automatic-ripping-machine/wiki/apprise.yaml) (allows notifications to Discord, Slack, Telegram, Kodi, and lots of others)
+
+
+
+You can view the full sample file here  [arm.yaml](https://github.com/automatic-ripping-machine/automatic-ripping-machine/blob/main/setup/arm.yaml)
\ No newline at end of file
diff --git a/arm_wiki/docker.md b/arm_wiki/docker.md
new file mode 100644
index 000000000..3c88f1f84
--- /dev/null
+++ b/arm_wiki/docker.md
@@ -0,0 +1,55 @@
+## Installing ARM using Docker on Linux
+
+### **This is not compatible with the snap version of docker!**
+
+A pre-built image has been added to docker hub [HERE](https://hub.docker.com/repository/docker/automaticrippingmachine/automatic-ripping-machine).
+
+## Installing Linux
+- Select the option to install all third-party drivers
+- Make sure the username is `arm`
+
+## Prepare Linux
+If running in a VM, make sure all disks are available to your distro via hardware passthrough in the VM Hypervisor software and confirm all drives are showing up by running `lsscsi -g`
+
+**This script only supports Linux distros using the `apt` package manager.**
+
+```
+sudo apt install wget lsscsi
+lsscsi -g
+wget https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/main/scripts/docker-setup.sh
+sudo chmod +x docker-setup.sh
+```
+
+## Setup ARM Docker
+The script defaults to installing the `latest` tagged image from the `automaticrippingmachine` ARM from *DockerHub*.
+- To specify a tag, add `-t <tag>`
+- To specify a fork, add `-f <fork>`
+
+To install default: `sudo ./docker-setup.sh`  
+To install from a different repo, tag: `sudo ./docker-setup.sh -f automaticrippingmachine -t dev_build`
+
+The script will now:
+1. Create an `arm` user and group if they don't exist
+2. Install docker if it is not already found on the system
+3. Pull the appropriate image from Dockerhub
+4. Create host mountpoints for any DVD drives found on the system
+5. Save a copy of the template run command for the user to fill in to `~arm/start_arm_container.sh`
+
+## Post Install
+1. In a terminal session, 
+2. In a terminal session, type `id -u arm` and make a note of the returned value
+3. In a terminal session, type `id -g arm` and make a note of the returned value
+4. Open up `start_arm_container.sh` in the text editor of your choice. 
+    1. If the returned value of 1. is not 1000, enter that value for `ARM_UID`. If the returned value is 1000, delete that line from the script.
+    2. If the returned value of 2. is not 1000, enter that value for `ARM_GID`. If the returned value is 1000, delete that line from the script.
+    3. Fill in the appropriate paths for the volumes being mounted
+    4. Fill in the list of CPU core threads to give the container in `--cpuset-cpus`. It's highly recommended to leave at least one core for the hypervisor to use, so the host machine doesn't get choked out during transcoding! Also, CPUs with multiple threads per core will be numbered in pairs (e.g. passing only core #4 would be `--cpuset-cpus='5,6'`)
+    5. Save and close
+5. Run the container with `sudo ./start_arm_container.sh`
+
+You will then need to visit http://WEBSERVER_IP:PORT
+An admin account is required to view rips and settings. A default one has been created for you.
+
+Username: **admin**
+
+Password: **password**
diff --git a/arm_wiki/intel-qsv.md b/arm_wiki/intel-qsv.md
new file mode 100644
index 000000000..7f7518b41
--- /dev/null
+++ b/arm_wiki/intel-qsv.md
@@ -0,0 +1,60 @@
+# Adding Intel QuickSync Support
+
+Some distros may not enable Intel QuickSync Video by default in their packages of HandBrakeCLI. This needs to be added manually, this means rebuilding HandBrake from source.
+You can check if your version already came with QSV support by running 
+
+`HandBrakeCLI --help | grep -A12 "Select video encoder"`
+
+If QSV is enabled should give something similar to 
+
+```
+   -e, --encoder <string>  Select video encoder:
+                               x264
+                               x264_10bit
+                               qsv_h264
+                               x265
+                               x265_10bit
+                               x265_12bit
+                               qsv_h265
+                               mpeg4
+                               mpeg2
+                               VP8
+                               VP9
+HandBrake has exited.
+
+```
+
+If you don't see `qsv_h264` or `qsv_h265` your version of HandBrakeCLI might not have have QSV enabled when it was built. 
+This also could be that you don't have Intel Media SDK installed.
+
+The Intel Media SDK is required for QSV with HandBrake to work.
+
+So you can either try to find the Intel Media SDK package from your distro or you can build it from source.
+
+I have made a script that will Install all the requirements for Intel QSV to get up and running.
+
+You can either follow along the [commands](https://raw.githubusercontent.com/automatic-ripping-machine/automatic-ripping-machine/main/scripts/ubuntu-quicksync.sh) or you can run:
+
+ ```
+ sudo apt install wget
+ wget https://github.com/automatic-ripping-machine/automatic-ripping-machine/blob/main/scripts/ubuntu-quicksync.sh
+ sudo chmod +x ubuntu-quicksync.sh
+ sudo ./ubuntu-quicksync.sh
+ ```
+ Remember to `reboot` to complete installation.
+
+
+## After Installation
+Once you have verified everything installed correctly and the `qsv_264` or `qsv_265` show up when you run the HandBrakeCLI command above. You can set your profile in your arm.yaml config.
+
+There are 2 supported profiles for Intel QSV they are `H.265 QSV 1080p` OR `H.265 QSV 2160p 4K`
+
+You will also need to add the arm user to the video & render groups so that arm can access the QSV encoder
+```
+sudo usermod -a -G video arm 
+sudo usermod -a -G render arm
+```
+## HandBrake Official Documentation 
+For more detailed information you can read through the official HandBrake documentation [HandBrake Building for linux](https://handbrake.fr/docs/en/1.3.0/developer/build-linux.html)
+
+You can also use the flat-packs provided by HandBrake - More information from here [Flatpacks](https://handbrake.fr/docs/en/1.3.0/developer/flatpak-repo.html)
\ No newline at end of file
diff --git a/arm_wiki/nvidia.md b/arm_wiki/nvidia.md
new file mode 100644
index 000000000..530e86d01
--- /dev/null
+++ b/arm_wiki/nvidia.md
@@ -0,0 +1,106 @@
+# Checking for NVENC support
+Nvidia NVENC support comes with HandBrake in some distros, to check first make sure you have at least
+- GeForce GTX Pascal (1050+)
+- RTX Turing (1650+, 2060+) 
+- or later GPU.
+- drivers are updated to at least 418.81 or later.
+
+Testing if HandBrake recognizes your GPU - Run
+
+`HandBrakeCLI --help | grep -A12 "Select video encoder"`
+
+into your ssh/terminal window
+
+If NVENC is enabled should give something similar to
+```
+   -e, --encoder <string>  Select video encoder:
+                               x264
+                               x264_10bit
+                               nvenc_h264
+                               x265
+                               x265_10bit
+                               x265_12bit
+                               nvenc_h265
+                               nvenc_h265_10bit
+                               mpeg4
+                               mpeg2
+                               VP8
+                               VP9
+HandBrake has exited.
+```
+You can also check with 
+`HandBrakeCLI --version` and it should output
+
+```
+[23:37:19] Compile-time hardening features are enabled
+[23:37:19] nvenc: version 12.0 is available
+[23:37:19] nvdec: is not compiled into this build
+[23:37:19] hb_init: starting libhb thread
+[23:37:19] thread 7f002300e700 started ("libhb")
+HandBrake 20230130172537-a5238f484-master
+```
+
+## Cant see those options ?
+
+If you don't see the extra options for nvenc then you will need to build HandBrakeCLI from source.
+instructions can be found here: 
+
+First add all the dependencies from here:
+https://handbrake.fr/docs/en/latest/developer/install-dependencies-ubuntu.html
+
+and then when ready build handbrake following instructions from here: https://handbrake.fr/docs/en/latest/developer/build-linux.html
+
+## Installing NVIDIA drivers:
+Recommended to do immediately after installing ubuntu
+
+1. Installing the drivers on servers and/or for computing purposes
+`sudo ubuntu-drivers install --gpgpu`
+If you have a desktop environment install drop the --gpgpu
+
+2. Reboot system
+`sudo reboot`
+
+## Installing the NVIDIA Container Toolkit:
+Do this before point 5 in post installation guide for docker "Run the container with sudo ./start_arm_container.sh" 
+
+1. Adding the repository:
+`curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \
+  && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \
+    sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \
+    sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list` 
+    
+2. Update repository
+`sudo apt-get update`
+4. Install the NVIDIA Container Toolkit packages:
+`sudo apt-get install -y nvidia-container-toolkit`
+
+5. Configure the container runtime by using the nvidia-ctk command:
+`sudo nvidia-ctk runtime configure --runtime=docker`
+
+6. Restart the Docker daemon:
+`sudo systemctl restart docker`
+
+
+## Post install
+
+Once handbrake recognizes your GPU,
+You can use one of the 2 built in profiles in your arm.yaml config.
+
+`H.265 NVENC 2160p 4K` OR `H.265 NVENC 1080p`
+
+
+You will also need to add the arm user to the video & render groups so that arm can access the NVENC encoder
+```
+sudo usermod -a -G video arm 
+sudo usermod -a -G render arm
+```
+
+------
+## 🐋 - NVENC doesn't work
+
+Be sure that both variables for `NVIDIA_DRIVER_CAPABILITIES=all`
+and `--gpus all` are set as NVENC won't work without them
+
+## HandBrake Official Documentation 
+For more detailed information you can read through the official HandBrake documentation [HandBrake Building for linux](https://handbrake.fr/docs/en/1.3.0/developer/build-linux.html)
+
diff --git a/arm_wiki/related-howtos.md b/arm_wiki/related-howtos.md
new file mode 100644
index 000000000..1e2ea1992
--- /dev/null
+++ b/arm_wiki/related-howtos.md
@@ -0,0 +1,18 @@
+**Warning! Some of these may be old and outdated**
+
+ARM under LXC / Proxmox: 
+
+ - https://www.reddit.com/r/homelab/comments/7bgtu9/a_simple_solution_for_getting_automated_ripping/
+
+Ansible Role:
+
+- https://galaxy.ansible.com/jswetzen/automatic-ripping-machine/
+- https://github.com/jswetzen/automatic-ripping-machine-setup
+
+Dockers:
+
+- https://github.com/deekue/automatic-ripping-machine/tree/docker
+
+Linux Distros:
+
+- User submited install instructions for [Drauger OS](https://www.reddit.com/r/homelab/comments/ljxfkj/noob_friendly_installing_and_setting_up_automatic/?utm_source=share&utm_medium=web2x&context=3) (Reddit)
\ No newline at end of file
diff --git a/arm_wiki/upgrading.md b/arm_wiki/upgrading.md
new file mode 100644
index 000000000..f5ecbd2e1
--- /dev/null
+++ b/arm_wiki/upgrading.md
@@ -0,0 +1,52 @@
+# Command line update (newer versions)
+
+## First backup config files
+:bangbang: Backup config file and replace it with the updated config :bangbang:
+```bash
+mv /opt/arm/arm.yaml /MY/SAFE/PLACE/arm.yaml
+```
+You can than upgrade
+
+-------------------------------------
+
+## Update A.R.M (Version >v2.2)
+Shell/Terminal commands
+```
+cd /opt/arm
+git stash
+git pull
+# Remove old yaml file if it still exists
+rm arm.yaml
+# Copy new config file
+sudo cp docs/arm.yaml.sample arm.yaml
+# install any new packages
+sudo pip3 install -r requirements.txt
+sudo ln -s /opt/arm/arm.yaml /etc/arm/
+sudo ln -s /opt/arm/setup/.abcde.conf /home/arm/
+```
+This should update most of A.R.M, you will still need to restart the armui service if you have one installed.
+
+To do this run: `sudo systemctl restart armui` If you didn't install the service you can reboot, or find the running armui process and kill it.
+
+-------------------------------------
+## Upgrading From Very Old Versions (Pre v2.2)
+
+Upgrading is now possible from version as old as v2.0
+
+All you need to do is move all the new files from this repo into the arm folder `/opt/arm` 
+Then insert a disc to start the upgrade process. The process is almost fully automatic. You still need to insert a disc to start the process. 
+
+Sometimes the disc needs to be inserted/ejected twice for this to fully trigger.
+
+If this process fails to update the arm database you may need to run the arm command manually with a disc already inserted.
+
+`sudo -u arm /usr/bin/python3 /opt/arm/arm/ripper/main.py -d sr0`
+
+-------------------------------------
+### Notes...
+
+#### :small_red_triangle: Pre version 2.6
+- For your own clarity sake, it may be best to delete the folder `/opt/arm/arm/ui/static` completely before adding the files from this repo. 
+The reason this is recommended is that previous versions of ARM shipped with a lot of extra files that were not used at all.
+This made things slightly more cluttered, especially for users who want to customise or tinker with ARM. The newest version of ARM only ships with things it needs, and provides the sources so the end users can obtain those extra sources if they wish.
+- It should be possible to run the shell commands, but this hasn't been tested.
\ No newline at end of file
diff --git a/arm_wiki/workflow-diagram.md b/arm_wiki/workflow-diagram.md
new file mode 100644
index 000000000..ae17f7026
--- /dev/null
+++ b/arm_wiki/workflow-diagram.md
@@ -0,0 +1,3 @@
+# The ARM workflow diagram
+
+![ARM Workflow diagram](https://raw.githubusercontent.com/muckngrind4/arm_wiki/master/images/arm.png)
\ No newline at end of file