Astro + React islands + MDX with a theme system (terminal, concrete, nostromo, overgrowth), USMT Dash case study, work/log/sound/models/about/ contact pages, RSS, self-hosted contact form over SMTP, /media proxy to Nextcloud, Dockerfile for Coolify, and a GitHub Action that mirrors main to Gitea.
No files matched your search
@@ -0,0 +1,14 @@
|
||||
---
|
||||
title: 'Transmission 000: Boot Sequence'
|
||||
summary: Why this site exists, what it's built with, and what's going in the log each week.
|
||||
date: 2026-10-08
|
||||
tags: [meta, site]
|
||||
---
|
||||
|
||||
Placeholder for the first weekly log entry.
|
||||
|
||||
This site is built with Astro, React islands and plain CSS. It runs in a Docker container on
|
||||
my own Coolify server, and the heavy media (game builds, recordings, 3D models) is served
|
||||
from my NAS.
|
||||
|
||||
Each week I'll post what I worked on: code, builds, models and music.
|
||||
@@ -0,0 +1,5 @@
|
||||
title: Placeholder Model
|
||||
date: 2026-10-01
|
||||
file: models/placeholder.glb
|
||||
tools: [Blender]
|
||||
notes: Export from Blender as .glb (Draco compression on), upload under models/ in the media share.
|
||||
@@ -0,0 +1,5 @@
|
||||
title: Placeholder Take
|
||||
date: 2026-10-01
|
||||
file: sound/placeholder-take.mp3
|
||||
notes: Upload an mp3/ogg/flac to the media share under sound/ and point `file` at it.
|
||||
gear: [Guitar, Interface]
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
title: Chicago in 3D
|
||||
summary: An architectural tour of the city. Chicago landmarks modeled in Blender and explored in the browser, with the history and trivia for each building.
|
||||
disciplines: [3d, web]
|
||||
stack: [React, Three.js, Blender]
|
||||
date: 2026-06-01
|
||||
status: in-progress
|
||||
placeholder: true
|
||||
theme: concrete
|
||||
---
|
||||
|
||||
Placeholder. Write-up coming soon, with an interactive viewer for the city map.
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
title: Hardware Build
|
||||
summary: Placeholder for a physical engineering project, with photos, schematics and a build log.
|
||||
disciplines: [hardware]
|
||||
stack: []
|
||||
date: 2025-09-01
|
||||
status: shipped
|
||||
placeholder: true
|
||||
theme: concrete
|
||||
---
|
||||
|
||||
Placeholder.
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
title: Homelab Infrastructure
|
||||
summary: Self-hosted file storage, budgeting, receipts and password management for family and friends, running on Docker, Podman and LXC on Proxmox.
|
||||
disciplines: [software, hardware]
|
||||
stack: [Proxmox, Docker, Podman, LXC, NixOS, Coolify, Gitea]
|
||||
date: 2025-04-01
|
||||
status: live
|
||||
placeholder: true
|
||||
theme: nostromo
|
||||
---
|
||||
|
||||
Placeholder. A write-up of the rack, the network and the services is coming soon.
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: Untitled Game
|
||||
summary: Placeholder for a Godot or Unity game. Once a web build is uploaded to the media share, it becomes playable right here.
|
||||
disciplines: [game]
|
||||
stack: [Godot]
|
||||
date: 2026-01-01
|
||||
status: in-progress
|
||||
placeholder: true
|
||||
theme: overgrowth
|
||||
# Uncomment when a web export is uploaded to <media share>/games/untitled-game/
|
||||
# game:
|
||||
# engine: godot
|
||||
# path: games/untitled-game
|
||||
---
|
||||
|
||||
Placeholder.
|
||||
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 137 KiB |
|
After Width: | Height: | Size: 186 KiB |
|
After Width: | Height: | Size: 143 KiB |
@@ -0,0 +1,90 @@
|
||||
---
|
||||
title: USMT Dash
|
||||
summary: A real-time migration dashboard over SCCM that took a six-person refresh team from about 10 builds a day to 25. PowerShell from end to end, with a live public demo.
|
||||
disciplines: [software, web]
|
||||
stack: [PowerShell, HttpListener, SQL (ConfigMgr), Active Directory, HTML/JS, Docker, Coolify]
|
||||
date: 2026-08-01
|
||||
status: live
|
||||
role: Sole developer · Technical lead
|
||||
cover: ./overview.png
|
||||
coverAlt: USMT Dash overview page showing issue counters, progress, a building and floor map and a deployment calendar.
|
||||
featured: true
|
||||
links:
|
||||
- { label: Live demo, href: 'https://usmt.yoyos.sh' }
|
||||
- { label: Source, href: 'https://gitea.yoyos.sh/yoyos/usmt-dash' }
|
||||
---
|
||||
|
||||
import Figure from '../../../components/Figure.astro';
|
||||
import Gallery from '../../../components/Gallery.astro';
|
||||
import overview from './overview.png';
|
||||
import status from './usmt-status.png';
|
||||
import terminals from './terminals.png';
|
||||
import software from './missing-software.png';
|
||||
import custom from './custom-view.png';
|
||||
import details from './device-details.png';
|
||||
import docs from './documentation.png';
|
||||
import architecture from './architecture.png';
|
||||
|
||||
## The problem
|
||||
|
||||
On a large hardware refresh, every old PC gets backed up with USMT, paired with its new
|
||||
machine in ConfigMgr (SCCM), and restored. Checking a single device in the ConfigMgr console
|
||||
took about **a minute**: is the association there, did the backup start, is the box even on
|
||||
the network? On a 1,300-device refresh with a six-person team, those minutes added up to the
|
||||
bottleneck.
|
||||
|
||||
## What I built
|
||||
|
||||
USMT Dash is one shared live view of the whole refresh. Every device answers in **under a
|
||||
second**, and the overview page is built to drive the refresh's open issues to zero.
|
||||
|
||||
<Figure src={overview} alt="Overview page" caption="Overview: issue counters, progress, a building × floor map, and a calendar of deployment-date tags." />
|
||||
|
||||
It's **PowerShell from end to end**, with no web framework, database server or runtime
|
||||
beyond PowerShell. That was deliberate: it had to run on locked-down hospital
|
||||
infrastructure where installing a stack wasn't an option.
|
||||
|
||||
- **Server:** a `System.Net.HttpListener` web server with a 17-route JSON API, IP allowlist and gzip.
|
||||
- **Worker:** a polling loop that queries SCCM's SQL database, Active Directory, DNS/ICMP and admin shares, works out each device's state, and writes JSON.
|
||||
- **Front end:** a single-file HTML/JS dashboard of about 4,600 lines, with routing, Excel-style filters, a knowledge base and a mobile card layout.
|
||||
|
||||
<Figure src={architecture} alt="Architecture diagram" caption="The server and worker never talk directly. The Data folder is the entire interface between them." />
|
||||
|
||||
## Details that mattered
|
||||
|
||||
- **A smart status engine.** It combines ConfigMgr's `MigrationStatus` with whether the
|
||||
USMT progress log is actively being written, so "in progress" means in progress.
|
||||
- **Network checks that tell the truth.** It resolves *all* A records, pings each one and
|
||||
validates reverse DNS, which separates *Online*, *Timed Out*, *Not Found* and *DNS Issue*
|
||||
(a stale record pointing at a different machine).
|
||||
- **Missing software.** It diffs installed software between the source and destination
|
||||
machines, filters out the baseline image and groups suites, so a technician sees only the
|
||||
specialty apps still left to install.
|
||||
- **Live while it works.** Rows publish every few seconds during a sweep, newly tracked
|
||||
devices go first, and the worker sleeps overnight with a midnight pitstop for the software
|
||||
refresh.
|
||||
|
||||
<Gallery>
|
||||
<Figure src={status} alt="USMT Status page" caption="Every migration grouped by state." />
|
||||
<Figure src={software} alt="Missing software view" caption="Specialty apps still missing on the new machine." />
|
||||
<Figure src={details} alt="Device details dialog" caption="Both sides of a migration, with a reason for every blank." />
|
||||
<Figure src={custom} alt="Custom view builder" caption="Build-your-own table from any field." />
|
||||
<Figure src={docs} alt="Knowledge base" caption="Built-in Markdown knowledge base." />
|
||||
<Figure src={terminals} alt="Terminal panel" caption="The demo streams the real server and worker consoles." />
|
||||
</Gallery>
|
||||
|
||||
## The public demo
|
||||
|
||||
The [hosted demo](https://usmt.yoyos.sh) runs the **unmodified** server and worker in a
|
||||
container against a simulated 200-device fleet. A demo provider replaces the SCCM provider,
|
||||
and that is the only difference. A simulated team tags, reschedules and fixes devices
|
||||
through the day. Visitor changes stay in their own browser (IndexedDB) and the API is
|
||||
read-only, so there is nothing to moderate or inject. It deploys from Gitea to Coolify like
|
||||
everything else I host.
|
||||
|
||||
## Outcome
|
||||
|
||||
Shipped halfway through the Lurie Children's FY26 refresh. Daily builds went from roughly
|
||||
**10 to 25**, and the project closed **about 1,900 machines against a 1,300-device scope**,
|
||||
under budget.
|
||||
|
||||
|
After Width: | Height: | Size: 226 KiB |
|
After Width: | Height: | Size: 143 KiB |
|
After Width: | Height: | Size: 190 KiB |
|
After Width: | Height: | Size: 226 KiB |
@@ -0,0 +1,12 @@
|
||||
---
|
||||
title: Trainer Booking Site
|
||||
summary: A trainer booking site for XSport Fitness Gold Coast. It pulls open session times out of an HTML-only internal scheduler into browsable trainer profiles. Bookings rose 50% in the first month.
|
||||
disciplines: [web]
|
||||
stack: [React, Tailwind, Node.js]
|
||||
date: 2023-05-01
|
||||
status: archived
|
||||
role: Contract web developer
|
||||
placeholder: true
|
||||
---
|
||||
|
||||
Placeholder. The case study is coming soon.
|
||||