Started 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.git679906e/var/www/blut24.com/web/releases/2-679906e2-679906ehttps://jenkins.younex.de/job/blut24-landing/2/artifacthttps://jenkins.younex.de/job/blut24-landing/changeshttps://jenkins.younex.de/job/blut24-landing/2/https://jenkins.younex.de/job/blut24-landing/2/testReportfalseCheckoutGuard: main onlyShip source to targetBuild, health-check and swapSmoke testfalse#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/infoinfoinfofalseStarted by GitHub push by younex1Started by an SCM changeStarted by an SCM change33365492e0eebdab580a2e8c2b0c0eea00e89d6063365492e0eebdab580a2e8c2b0c0eea00e89d606refs/remotes/origin/main3365492e0eebdab580a2e8c2b0c0eea00e89d6063365492e0eebdab580a2e8c2b0c0eea00e89d606refs/remotes/origin/main3365492e0eebdab580a2e8c2b0c0eea00e89d6063365492e0eebdab580a2e8c2b0c0eea00e89d606refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#3 33654923235028038blut24-landing #3 33654923false35444SUCCESS1785220314292https://jenkins.younex.de/job/blut24-landing/3/.env.exampleserver/utils/registrationValidation.tsserver/api/registration/submit.post.tsd91c3a46ec2b1420a63ba8ecab63a9cb215936161785219798000https://jenkins.younex.de/user/infoinfoinfo@logyou.deregistration: operator test domains may register for any clinic Adds REGISTRATION_TEST_DOMAINS (comma-separated). Addresses on those domains skip the "e-mail domain belongs to the chosen Standort" check, so the flow can be exercised end-to-end against arbitrary clinics. That check is the only thing preventing a stranger from registering someone else's hospital, so it is never relaxed for real users. The bypass therefore: - does not exist at all when the variable is empty or unset (the default) - never counts as domain-verified (domain_verified stays 0) - forces needs_manual_approval and prefixes the note with [TESTREGISTRIERUNG via <domain>] - leaves the freemail blocklist and the per-Standort duplicate guard intact Verified: younex.de/it-beratung.it accepted for a non-matching Charité Standort; a non-whitelisted business domain and a freemail address both still rejected; and with the variable unset younex.de is rejected again. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> 2026-07-28 08:23:18 +0200d91c3a46ec2b1420a63ba8ecab63a9cb21593616registration: operator test domains may register for any cliniceditserver/utils/registrationValidation.tseditserver/api/registration/submit.post.tsedit.env.exampleJenkinsfiledeploy/deploy.sh3365492e0eebdab580a2e8c2b0c0eea00e89d6061785220306000https://jenkins.younex.de/user/infoinfoinfo@logyou.deci: move the deploy concurrency guard from Jenkins to the target Every build after the first sat in the queue as a BlockedItem and never started until Jenkins was restarted - observed three times on this controller. The only plausible cause was disableConcurrentBuilds(), so it is removed. The race it guarded against is two deploys swapping the `current` symlink at the same time. That resource lives on the TARGET, not on Jenkins, so deploy.sh now takes an flock on /var/lock/blut24-landing-deploy.lock for the whole run. That is strictly better: it also covers deploys started by hand or from another controller, which the Jenkins-side option never did. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> 2026-07-28 08:31:46 +02003365492e0eebdab580a2e8c2b0c0eea00e89d606ci: move the deploy concurrency guard from Jenkins to the targeteditJenkinsfileeditdeploy/deploy.shgithttps://jenkins.younex.de/user/infoinfofalse4https://jenkins.younex.de/job/blut24-landing/4/2https://jenkins.younex.de/job/blut24-landing/2/Started by GitHub push by younex11091770a6c5138113b51582d5bd5e86c607cbe262091770a6c5138113b51582d5bd5e86c607cbe262refs/remotes/origin/main091770a6c5138113b51582d5bd5e86c607cbe262091770a6c5138113b51582d5bd5e86c607cbe262refs/remotes/origin/main091770a6c5138113b51582d5bd5e86c607cbe262091770a6c5138113b51582d5bd5e86c607cbe262refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#1 091770a3025428038blut24-landing #1 091770a1false15439SUCCESS1785192514932https://jenkins.younex.de/job/blut24-landing/1/false2https://jenkins.younex.de/job/blut24-landing/2/