Runtime Diagnostics

Git Web Manager

Verify that required runtimes and tools are available on the server.

Scheduler Settings Node.js Processes

Overview

Runtime Diagnostics is available in System → Settings → Diagnostics. It detects the version and path of every runtime and build tool GWM depends on and surfaces that information in one place so you can confirm your server environment is ready before deploying.

Detected Runtimes

GWM checks for the following binaries on every diagnostics page load:

  • PHP — required for the GWM application itself.
  • Composer — used when deploying PHP projects that include a composer.json.
  • npm — used for JavaScript/Node.js project builds.
  • Python / python3 / py — used for Python project deployments.
  • pip / pip3 — used to install Python dependencies from requirements.txt.

Each entry shows the detected version string and full binary path, or a Not found badge if the binary is missing from the system PATH.

Re-Check

Click Re-check to re-run detection without reloading the page. Use this after installing a new runtime to confirm it is discoverable.

Per-Binary Install Guidance

When a binary is not found, GWM displays OS-specific installation instructions inline — covering Ubuntu/Debian, Alpine, macOS (Homebrew), and Windows. This is informational only; GWM does not run the install commands for you.

Node.js is the exception — GWM can install and manage the Node.js LTS runtime directly from System → Plugins without requiring root access. See the Plugins page for details on installation, auto-update, and vulnerability scanning.

Troubleshooting

  • If a binary is installed but shows as Not found, it may not be on the PATH available to the web server user. Add the binary directory to that user's PATH and click Re-check.
  • For Python, GWM searches for python3, python, and py -3 in that order. Make sure at least one resolves.
  • For Composer, ensure the global composer binary is on PATH. A project-local vendor/bin/composer is not used here.