buildx.sh

Deploy a Hugo site to Codeberg Pages

Sun, 17 May 2026 00:00:00 +0000

Codeberg Pages publishes whatever sits on a branch named pages. So a deploy is just: build, then force-push the output to that branch. No CI runner, no API tokens — your existing SSH key does the auth.

#!/usr/bin/env bash
# Build a Hugo site and deploy it to Codeberg Pages by force-pushing the
# built public/ directory to the `pages` branch of the pages repo.
set -euo pipefail
cd "$(dirname "$0")/.."

SITE_URL="https://USER.codeberg.page/"
REMOTE="git@codeberg.org:USER/pages.git"
BRANCH="pages"

# Build with the live baseURL so absolute asset links resolve correctly.
hugo --minify --gc --cleanDestinationDir --baseURL "$SITE_URL"

# Publish public/ as a single fresh commit, force-pushed to the pages branch.
# Force-push means the branch always mirrors the latest build — no stale files.
rm -rf public/.git
git -C public init -q
git -C public checkout -q -B "$BRANCH"
git -C public add -A
git -C public \
 -c user.name="deploy" \
 -c user.email="deploy@example.com" \
 commit -q -m "deploy: $(date -u +%Y-%m-%dT%H:%M:%SZ)"
git -C public push -q -f "$REMOTE" "HEAD:${BRANCH}"
rm -rf public/.git

echo "deployed -> $SITE_URL"

Swap USER for your Codeberg user or org. Three things have to be true first:

Find the largest objects in git history

Sat, 16 May 2026 00:00:00 +0000

A repo feels heavy and du on the working tree shows nothing. The weight is in history — a committed binary, a stray dump, a vendored archive. This lists the 20 biggest blobs across all commits, including deleted ones.

#!/usr/bin/env bash
# git-fat — list the 20 largest objects in git history, human-readable.
set -euo pipefail

git rev-list --objects --all |
 git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' |
 awk '$1 == "blob" { print $3, $4 }' |
 sort -rn |
 head -20 |
 numfmt --to=iec --field=1 |
 column -t

Output is size path, biggest first:

Retry a command with exponential backoff

Thu, 14 May 2026 00:00:00 +0000

Network calls fail for a second and then work fine. A script shouldn’t die over that. This wraps any command, retrying with a doubling delay.

# retry — run a command up to N times with exponential backoff.
# Usage: retry 5 curl -sf https://example.com
retry() {
 local max="$1"; shift
 local n=1 delay=1
 until "$@"; do
 if (( n >= max )); then
 echo "retry: '$*' failed after $max attempts" >&2
 return 1
 fi
 echo "retry: attempt $n failed; sleeping ${delay}s" >&2
 sleep "$delay"
 (( n++, delay *= 2 ))
 done
}

It returns the command’s success once it passes, or 1 after exhausting the attempts — so it drops straight into a set -e script:

Read one secret from a SOPS file

Tue, 12 May 2026 00:00:00 +0000

sops -d prints the entire decrypted file. Most of the time you want exactly one value — and you don’t want it landing in shell history or a temp file. --extract does that.

# secret — print one key from a SOPS-encrypted YAML file.
# Usage: secret CODEBERG_TOKEN [path/to/secrets.enc.yaml]
secret() {
 local key="$1" file="${2:-secrets.enc.yaml}"
 sops -d --extract "[\"${key}\"]" "$file"
}

Use it inline so the plaintext never touches disk and an env var still wins:

Auto-load a Nix flake dev shell with direnv

Sat, 09 May 2026 00:00:00 +0000

A project’s tools should appear when you enter its directory and vanish when you leave. direnv + nix-direnv does exactly that — this .envrc loads a named flake dev shell on cd.

# .envrc — auto-load a named Nix flake dev shell.
# Needs direnv + nix-direnv: https://github.com/nix-community/nix-direnv

if ! has nix_direnv_version || ! nix_direnv_version 3.0.0; then
 source_url "https://raw.githubusercontent.com/nix-community/nix-direnv/3.0.0/direnvrc" \
 "sha256-21TMnI2xWX7HkSTjFFri2UaohXVj854mgvWapWrxRXg="
fi

# Loads devShells.<system>.myshell — drop the suffix for the default shell.
use flake .#myshell

# Untracked local overrides, if any.
[ -f .envrc.local ] && source_env .envrc.local

Run direnv allow once; after that the shell rebuilds itself whenever flake.nix changes.

About

Wed, 06 May 2026 00:00:00 +0000

buildx.sh is a notebook for building things.

The mental model is simple: build with effect, with performance, and with fun. If a project loses any of the three, it stops being worth doing.

Why this exists

Most “how I built X” posts skip the parts that actually matter — the trade-offs, the failed attempts, the moment you realize the architecture is wrong. This site keeps those parts in.

What lives here

Build logs for side projects
Performance experiments and benchmarks
Short opinions on tools and tradeoffs
The occasional rant, kept brief

Get in touch

Open a thread, send a message, or just borrow an idea. Building is more fun together.

Hello, buildx

Wed, 06 May 2026 00:00:00 +0000

$ buildx --help
Usage: buildx [thing]

Build everything. With effect. With speed. With fun.

Welcome to buildx.sh — a place to build things and write down what worked.

The mental model

Three knobs, always tuned together:

Effective — does it solve the actual problem, end to end?
High performance — is it fast enough to enjoy using?
Fun — would you reach for it again on a Saturday?

Drop any one of them and the project quietly dies. Keep all three honest, and small projects start compounding into a craft.