Started by GitHub push by younex1488fb8db79ff790ff6f298d61b279dade9abc8b3b88fb8db79ff790ff6f298d61b279dade9abc8b3brefs/remotes/origin/main88fb8db79ff790ff6f298d61b279dade9abc8b3b88fb8db79ff790ff6f298d61b279dade9abc8b3brefs/remotes/origin/main88fb8db79ff790ff6f298d61b279dade9abc8b3b88fb8db79ff790ff6f298d61b279dade9abc8b3brefs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.git88fb8db/var/www/blut24.com/web/releases/4-88fb8db4-88fb8dbhttps://jenkins.younex.de/job/blut24-landing/4/artifacthttps://jenkins.younex.de/job/blut24-landing/changeshttps://jenkins.younex.de/job/blut24-landing/4/https://jenkins.younex.de/job/blut24-landing/4/testReportfalseCheckoutGuard: main onlyShip source to targetBuild, health-check and swapSmoke testfalse#4 88fb8db2625228038blut24-landing #4 88fb8db4false45446SUCCESS1785223605276https://jenkins.younex.de/job/blut24-landing/4/- app/components/SiteFooter.vueapp/components/AndroidBadge.vueapp/components/SectionApp.vue88fb8db79ff790ff6f298d61b279dade9abc8b3b1785223594000https://jenkins.younex.de/user/infoinfoinfo@logyou.delanding: proper Android download badge, reused in the footer
Replaces the flat outline-icon button with a badge in the visual language people
actually recognise: dark pill, mark on the left, small kicker over a bold line,
and the Android robot drawn inline in its own green (#3DDC84).
Deliberately NOT the official "Get it on Google Play" badge. That artwork is
Google's trademark and licensed only for links pointing at a Play Store listing;
this link is a direct APK download, so copying it would be both a trademark
problem and a false claim to the visitor. Same recognition, honest wording
("Direkt-Download / Android APK").
Extracted as AndroidBadge.vue with a `compact` variant so the app section and the
footer cannot drift apart. Until an APK exists the badge renders as a disabled
span (not a dead link) with its own aria-label; set `available` to switch it on.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 09:26:34 +020088fb8db79ff790ff6f298d61b279dade9abc8b3blanding: proper Android download badge, reused in the footeraddapp/components/AndroidBadge.vueeditapp/components/SiteFooter.vueeditapp/components/SectionApp.vue
githttps://jenkins.younex.de/user/infoinfoinfofalseStarted by GitHub push by younex159d957078b237f5dd9f22e2d14badac3ff8e33bd69d957078b237f5dd9f22e2d14badac3ff8e33bd6refs/remotes/origin/main9d957078b237f5dd9f22e2d14badac3ff8e33bd69d957078b237f5dd9f22e2d14badac3ff8e33bd6refs/remotes/origin/main9d957078b237f5dd9f22e2d14badac3ff8e33bd69d957078b237f5dd9f22e2d14badac3ff8e33bd6refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#5 9d957072664528038blut24-landing #5 9d957075false55449SUCCESS1785227610682https://jenkins.younex.de/job/blut24-landing/5/- deploy/README.mdapp/app.vueapp/components/SectionHero.vueserver/api/registration/submit.post.tsapp/components/SiteFooter.vueapp/components/SiteHeader.vueapp/components/SectionRegistration.vueapp/pages/datenschutz.vueREADME.mdapp/components/SectionCourier.vue.idea/vcs.xmlapp/components/SectionApp.vueapp/components/RegistrationDialog.vueserver/utils/registrationValidation.tsscripts/test-registration.mjsapp/composables/useRegistrationDialog.tsserver/utils/registrationDb.tsapp/components/AndroidBadge.vueapp/components/AppIcon.vueapp/components/RegistrationForm.vuedeploy/nginx-blut24.confapp/components/SectionProof.vue9d957078b237f5dd9f22e2d14badac3ff8e33bd61785227601000https://jenkins.younex.de/user/infoinfoinfo@logyou.delanding: modal registration, value-led proof band, autocomplete fix, APK live
- Registration moved into a native <dialog> modal driven from every CTA, with
focus trap/return, scroll lock, backdrop + ESC dismissal, full-screen sheet on
mobile and prefers-reduced-motion respected.
- Replaced the data-source stats ("Quelle: Bundes-Klinik-Atlas", 293, 906) with
three statements of what the product actually does. No invented metrics: the
only figure left is the real 1.581 Klinik-Atlas count that was already there.
- Fixed the autocomplete staying open after a clinic was picked. Root cause was
watch(query): selecting wrote the label back into the field, which the watcher
read as a new search and reopened the list ~220ms later. The input is now
:value + @input so a programmatic write cannot be a search intent, with a
pendingQuery flag gating every path that opens the list.
- Removed Anrede end-to-end. The DB column is deliberately NOT migrated: it keeps
its NOT NULL DEFAULT '' so inserts that omit it stay valid on existing databases.
- Android badge switched live: the APK is published at
https://blut24.com/downloads/blut24-mobile.apk and served from disk by nginx
with the correct package MIME type.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 10:33:21 +02009d957078b237f5dd9f22e2d14badac3ff8e33bd6landing: modal registration, value-led proof band, autocomplete fix, APK liveeditapp/components/AppIcon.vueeditapp/components/SectionHero.vueeditapp/components/SiteFooter.vueeditapp/components/SiteHeader.vueeditserver/utils/registrationValidation.tseditapp/app.vueeditapp/components/SectionCourier.vueeditscripts/test-registration.mjseditdeploy/README.mdeditapp/components/RegistrationForm.vueadd.idea/vcs.xmleditapp/components/SectionProof.vueaddapp/components/RegistrationDialog.vueeditREADME.mdeditapp/components/SectionApp.vueeditapp/pages/datenschutz.vueeditdeploy/nginx-blut24.confaddapp/composables/useRegistrationDialog.tseditserver/api/registration/submit.post.tseditapp/components/SectionRegistration.vueeditserver/utils/registrationDb.tseditapp/components/AndroidBadge.vue
githttps://jenkins.younex.de/user/infoinfofalse6https://jenkins.younex.de/job/blut24-landing/6/4https://jenkins.younex.de/job/blut24-landing/4/Started 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.example
- Jenkinsfiledeploy/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.sh
githttps://jenkins.younex.de/user/infoinfofalse4https://jenkins.younex.de/job/blut24-landing/4/2https://jenkins.younex.de/job/blut24-landing/2/