Corrections around locations of exes

Author: ChrisMaunder

.vscode/launch.docker.json

@@ -93,7 +93,8 @@
             },
             "name": "ALPR",
             "type": "python",
-            "python": "/app/modules/ALPR/bin/linux/python38/venv/bin/python",
+            // "python": "/app/modules/ALPR/bin/ubuntu/python38/venv/bin/python",
+            "python": "/app/modules/ALPR/bin/debian/python38/venv/bin/python",
             "request": "launch",
             "program": "ALPR_adapter.py",
             "console": "integratedTerminal",

src/server/Modules/ModuleSettings.cs

@@ -180,14 +180,14 @@ public string GetFilePath(ModuleConfig module)
 
             // If it is a Python3X command then replace our marker in the default python path to
             // match the requested interpreter location in order to build the 
-            // "/runtimes/bin/linux/python38/venv/bin/python3" path.
+            // "/runtimes/bin/ubuntu/python38/venv/bin/python3" path.
             if (runtime.StartsWith("python"))
             {
                 // HACK: In Docker, Python installations for modules can be local for downloaded
                 // modules, or shared for pre-installed modules. For preinstalled modules hardcoded
                 // into the Docker image, the python runtimes and package are installs at the
                 // system level, and not in a virtual environment. This means Python command is in
-                // the format of "python3.N" rather than "/runtimes/bin/linux/python3N/venv/bin/python3"
+                // the format of "python3.N" rather than "/runtimes/bin/ubuntu/python3N/venv/bin/python3"
                 // ie. Python runtime location is 'System'.
                 if (SystemInfo.IsDocker)
                 {