- HTML 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| deploy | ||
| .woodpecker.yml | ||
| index.html | ||
| README.md | ||
bartdupon
Tiny landing page for bartdupon.net that forwards to my Git profile (git.m44.be/bdu) while loading Umami analytics first.
Why a page instead of a plain redirect: a real HTTP 301 never loads the
page, so no analytics can run. This serves an HTML page (HTTP 200) that
fires the Umami beacon, then redirects client-side via
location.replace(). A <meta refresh> + visible link cover no-JS.
Reference tracking
Use the domain as a referral source on other sites:
https://bartdupon.net?ref=m44
Umami's auto pageview is disabled (data-auto-track="false"). Each visit
sends a single custom event redirect with { ref }, where ref
defaults to "direct" when the query param is absent. Group the
redirect event by ref in Umami to see traffic per referral source.
Layout
index.html the redirect + tracking page
deploy/dockerfile nginx:alpine serving index.html
deploy/nginx.conf serves the page + proxies /umami/* to umami.m44.be
deploy/docker-compose.yml Traefik labels for bartdupon.net (+ www → apex)
.woodpecker.yml CI: build image + compose up on push to main
Umami
The data-website-id in index.html is the Umami site id for
bartdupon.net. It's a public, client-side identifier (visible in page
source), so it's hardcoded rather than injected from a secret.