Hosted by Netlify

Tue, 27 Oct 2026 16:41:01 +1100

How to deploy to Netlify Link to heading

I’m practicing multicloud deployments and want to host this blog on Netlify.

Create netlify.toml in blog repo on GitLab Link to heading

[build.environment]
DART_SASS_VERSION = "1.105.1"
GO_VERSION = "1.27.2"
HUGO_VERSION = "0.168.0"
NODE_VERSION = "24.21.0"
TZ = "Europe/Oslo"

[build]
publish = "public"
command = """\
 curl -sfLO "https://github.com/sass/dart-sass/releases/download/${DART_SASS_VERSION}/dart-sass-${DART_SASS_VERSION}-linux-x64.tar.gz" && \
 tar -C "${HOME}/.local" -xf "dart-sass-${DART_SASS_VERSION}-linux-x64.tar.gz" && \
 rm "dart-sass-${DART_SASS_VERSION}-linux-x64.tar.gz" && \
 export PATH="${HOME}/.local/dart-sass:${PATH}" && \
 git config --global core.quotepath false && \
 hugo build --gc --minify --baseURL "${URL}"
 """

Configure Netlify Link to heading

Create a project by importing from GitLab
Name the project ps4b→blog URL becomes https://ps4bp.netlify.app

References Link to heading

Cloudflare Turnstile

Tue, 27 Oct 2026 11:45:01 +1100

Put a gate in a worker Link to heading

Create a Turnstile widget. In the Cloudflare dashboard, open Turnstile → Add worker-captcha manually. Add forex-proxy.ps4bp.workers.dev as an allowed hostname and copy the sitekey and secret key. The sitekey is public; keep the secret private.
Store the keys as Worker variables. In Workers & Pages → forex-proxy → Settings → Runtime variables and Secrets, add:
- TURNSTILE_SITE_KEY as a regular text variable.
- TURNSTILE_SECRET_KEY as a secret.
Make the Worker handle requests before serving the page. Have it:
- Check for a valid pass cookie on each page request.
- If there isn’t one, return a small HTML verification page containing the Turnstile widget.
- Accept the widget token at a verification endpoint and send it to https://challenges.cloudflare.com/turnstile/v0/siteverify.
- Only after Siteverify returns success: true, issue a short-lived, signed pass cookie and redirect back to /.
- Serve index.html when the cookie is valid.
Protect every route that should be gated. If only the landing page needs protection, gate /. If API routes also need protection, gate those separately so the verification endpoint stays reachable.
Deploy and check both paths. Test that a fresh browser sees the challenge, a successful verification reaches the page, and a request without a valid cookie cannot fetch the protected content directly.

Multicloud on ps4bp

Hosted by Netlify

How to deploy to Netlify Link to heading

Create netlify.toml in blog repo on GitLab Link to heading

Configure Netlify Link to heading

References Link to heading

Cloudflare Turnstile

Put a gate in a worker Link to heading