SPANDAMAN HEADLESSVIDX CPANEL SETUP

Use these exact cPanel Node.js values for the apps.spandaman.co.uk subdomain:

Application root:
apps.spandaman.co.uk/spandaman/current/HeadlessVidX

Application URL:
/spandaman/current/HeadlessVidX

Application startup file:
index.js

Node.js version:
20.x

Then:
1. Save the app.
2. Run NPM install from cPanel.
3. Restart the Node application.
4. Open https://apps.spandaman.co.uk/spandaman/current/HeadlessVidX/ping and confirm Pong/ok.
5. Open https://apps.spandaman.co.uk/spandaman/current/spandaman_headlessvidx_status.php and confirm online=true. browser_ready=true means full browser extraction works; direct_media_fallback_ready=true means direct MP4/HLS/TS resolution works even if cPanel is missing Playwright GUI libraries.

If cPanel shows "No such application or it's broken" or "Unable to find app venv folder", remove/recreate the Node.js application with the same values above, then run NPM Install again. That error means the cPanel-managed app environment is missing, not that the SPANDAMAN playlist host files are broken.

Do not set Application root to the main-domain spandaman/current path for this hosted app.
Do not set the startup file to HeadlessVidX/index.js when the application root already ends in HeadlessVidX.
FTP upload deploys the files but cannot register or repair the persistent cPanel Node service environment.
FTP upload also cannot reliably install missing host OS browser libraries such as libgtk/libasound/Cairo/NSS. If browser_ready=false but direct_media_fallback_ready=true, keep HeadlessVidX in degraded browser-capture mode and use direct-media/BS4/FFmpeg fallbacks unless the host enables those Linux packages or a proven user-space LD_LIBRARY_PATH bundle.