Go port checker
A single-binary daemon that polls local HTTP services and reports downtime with low CPU and memory footprint.
$cat README.md↳01 / OVERVIEW
Experiments
Small tools, prototypes, and technical scripts built to test ideas, libraries, and tools in practice.
~/home/projects/experiments[ 01 / 04 ]lab / toolspreview
ASSETS / SCREENSHOTS
↳02 / CONTEXT
The context
A collection of small utilities, CLI scripts, and prototypes created while testing specific libraries, system APIs, or language features.
Building self-contained experiments makes it easier to measure behavior, test edge cases, and learn new tools before incorporating them into larger projects.
↳03 / WHAT I DID
What I did
/prototyping
Built standalone Go command-line tools to test local port probing and background health checks.
/automation
Wrote bash and awk scripts to parse access logs and extract request status counts.
/other
Tested embedded SQLite with TypeScript for local data storage without a dedicated database server.
↳04 / UNDER THE HOOD
Under the hood.
Log parsing scripts
Streams server log files through standard UNIX filters to calculate error frequencies and response latencies.
Embedded SQLite
Stores local metrics and script run history in a single file on disk, avoiding background daemon overhead.
↳05 / NOTES
Notes
What changed
Rewrote an initial Python log parser in Go to produce a single self-contained binary that runs without runtime dependencies.
What I learned
POSIX standard shell scripts are much more portable across minimal Linux server installations than scripts relying on bash-specific features.
What I'd do differently
Add basic automated test fixtures for log format variations earlier in the prototyping process.