ps4bp

Hugo upgrade

Wed, 28 Oct 2026 13:17:35 +1100

Time to upgrade Hugo today

PS> winget update --purge|grep -i hugo
Hugo (Extended) Hugo.Hugo.Extended 0.168.0        0.169.0        winget
PS> winget upgrade Hugo.Hugo.Extended
Found Hugo (Extended) [Hugo.Hugo.Extended] Version 0.169.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/gohugoio/hugo/releases/download/v0.169.0/hugo_extended_0.169.0_windows-amd64.zip
  ██████████████████████████████  22.5 MB / 22.5 MB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Starting package install...
Command line alias added: "hugo"
Successfully installed
PS> hugo version
hugo v0.169.0-1da10fc44701c566b1669cdb2d12638f155138bd+extended windows/amd64 BuildDate=2026-10-27T14:52:20Z VendorInfo=gohugoio

Update netlify.toml accordingly.

Auto-publish on commit

Tue, 27 Oct 2026 19:29:36 +1100

Problem Link to heading

When a Hugo content file contains:

title: "My New Blog Post"
date: 2026-10-27
draft: true

Hugo treats the content as unpublished. Running a standard build hugo will exclude all draft content from the generated site. This behavior is intentional and helps prevent unfinished articles from being published accidentally.

To preview, hugo server -D. The -D (or –buildDrafts) flag tells Hugo to include draft content during local development.

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.

About

Sun, 25 Oct 2026 20:47:08 -0400

I’m a developer versed in Python, JavaScript, and PowerShell. I enjoy exploring technology, automating processes, and documenting both successes and failures. This blog is where I share my journey, lessons learned, project write-ups, and the occasional debugging adventure.

PS4BP is short for Practical Software for Better Productivity.

Hello World

Sun, 25 Oct 2026 20:43:54 -0400

Welcome to my new blog.

This site is built with Hugo, themed with Coder, and hosted on GitLab Pages.

Projects

Mon, 01 Jan 0001 00:00:00 +0000

An eclectic playground of tiny projects to learn by doing:

🚀 My First SWA Link to heading

Stopped developing, but learned

Deploying a free Azure Static Web App with GitHub Actions
Sourcing a timeanddate.com clock in an iframe, inspired by Amy Kapernick’s talk
Using the title attribute to provide simple tooltips

🛠️ YADa (SPA) Link to heading

Actively developing and learning

Using GitHub Actions to deploy across multiple cloud platforms
Working around CORS limitations with a Worker-based proxy
- a Python worker
- a JavaScript worker
Using semantic HTML to improve accessibility and document structure