Started by GitHub push by younex11091770a6c5138113b51582d5bd5e86c607cbe262091770a6c5138113b51582d5bd5e86c607cbe262refs/remotes/origin/main091770a6c5138113b51582d5bd5e86c607cbe262091770a6c5138113b51582d5bd5e86c607cbe262refs/remotes/origin/main091770a6c5138113b51582d5bd5e86c607cbe262091770a6c5138113b51582d5bd5e86c607cbe262refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.git091770a/var/www/blut24.com/web/releases/1-091770a1-091770ahttps://jenkins.younex.de/job/blut24-landing/1/artifacthttps://jenkins.younex.de/job/blut24-landing/changeshttps://jenkins.younex.de/job/blut24-landing/1/https://jenkins.younex.de/job/blut24-landing/1/testReportfalseCheckoutGuard: main onlyShip source to targetBuild, health-check and swapSmoke testfalse#1 091770a3025428038blut24-landing #1 091770a1false15439SUCCESS1785192514932https://jenkins.younex.de/job/blut24-landing/1/falseStarted by GitHub push by younex1Started by GitHub push by younex1Started by an SCM changeStarted by an SCM change2679906e5db227bfa0d8a3ca5800418269ab474e8679906e5db227bfa0d8a3ca5800418269ab474e8refs/remotes/origin/main679906e5db227bfa0d8a3ca5800418269ab474e8679906e5db227bfa0d8a3ca5800418269ab474e8refs/remotes/origin/main679906e5db227bfa0d8a3ca5800418269ab474e8679906e5db227bfa0d8a3ca5800418269ab474e8refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#2 679906e3275028038blut24-landing #2 679906e2false25442SUCCESS1785218932906https://jenkins.younex.de/job/blut24-landing/2/deploy/deploy.shdeploy/bootstrap-server.shdeploy/ecosystem.config.cjs679906e5db227bfa0d8a3ca5800418269ab474e81785218244000https://jenkins.younex.de/user/infoinfoinfo@logyou.dedeploy: pin Node v22.22.3, self-heal the install, realign bootstrap to ISPConfig The first Jenkins build logged EBADENGINE warnings: several transitive deps (@babel/*, undici) require Node ^22.18 / >=22.19 while the pin was v22.14.0. Bumped to v22.22.3 — same NODE_MODULE_VERSION 127, so the better-sqlite3 native build stays compatible and no rebuild-from-scratch is forced. deploy.sh now runs `nvm install` rather than `nvm use`, so bumping the pin in git is sufficient; previously a new version would have failed the deploy outright with "N/A: version not yet installed". It also ensures pm2 exists for that Node build. bootstrap-server.sh still carried the pre-ISPConfig layout and, worse, would have written a standalone nginx vhost with the same server_name as the ISPConfig-generated one - a collision that ISPConfig would regenerate away. It now creates the real layout (code in the docroot, secrets and SQLite in the site's private/ dir) and only REPORTS on the proxy block instead of fighting the panel for ownership. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> 2026-07-28 07:57:24 +0200679906e5db227bfa0d8a3ca5800418269ab474e8deploy: pin Node v22.22.3, self-heal the install, realign bootstrap to ISPConfigeditdeploy/deploy.sheditdeploy/bootstrap-server.sheditdeploy/ecosystem.config.cjsgithttps://jenkins.younex.de/user/infoinfofalse3https://jenkins.younex.de/job/blut24-landing/3/1https://jenkins.younex.de/job/blut24-landing/1/