claude
fbec36cb67
Scaffold the course repo and author the full curriculum in dependency-chain order, following the settled build decisions in handoff.md. - Scaffold: course README, vendor-neutral AGENTS.md (dogfoods Module 5), _TEMPLATE.md (the fixed 9-section module shape), root .gitignore, ship config. - Modules 1-2: reference exemplars (locked for tone/depth/lab style). - Modules 3-27: full lessons + runnable labs, each following the template, respecting the chain, vendor/model-agnostic, with "feel the pain" labs. - Module 8 hosting comparison web-researched and date-stamped (as of 2026-06-22), not written from memory; expansion-zone modules carry Verify-before-publish. - Capstone: the full loop end to end on the running tasks-app example. Lab code syntax-checked (Python/shell/YAML); every module has the 7 core template sections. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
74 lines
2.9 KiB
YAML
74 lines
2.9 KiB
YAML
# Module 19 lab — "Where did this actually run?"
|
|
#
|
|
# This is the Module 14 CI pipeline (lint + test the tasks-app) with one extra step bolted on the
|
|
# end: it makes the runner tell you who and where it is. Run it once on a hosted runner, then again
|
|
# after you've pointed it at your own self-hosted runner in Track B, and compare the two receipts.
|
|
#
|
|
# Where this file goes: the same workflow directory as your Module 14 ci.yml. On Actions-style forges
|
|
# (GitHub, and Forgejo/Gitea with Actions-compatible YAML) that's <forge-dir>/workflows/ at the repo
|
|
# root — e.g. .github/workflows/whoami-runner.yml. The filename is yours; the directory is not.
|
|
#
|
|
# For GitLab CI, the same idea is a one-job .gitlab-ci.yml: run the same script lines under `script:`
|
|
# with `tags:` selecting your runner. The shape rhymes; only the YAML dialect changes.
|
|
|
|
name: whoami-runner
|
|
|
|
on:
|
|
push:
|
|
workflow_dispatch: # lets you trigger it by hand from the forge UI
|
|
|
|
jobs:
|
|
whoami:
|
|
# Track A: leave this as the hosted image and read the receipt.
|
|
# Track B: change this to select your own runner by label, e.g.
|
|
# runs-on: [self-hosted, linux]
|
|
runs-on: ubuntu-latest
|
|
|
|
steps:
|
|
- name: Check out the code
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Set up Python
|
|
uses: actions/setup-python@v5
|
|
with:
|
|
python-version: "3.12"
|
|
|
|
- name: Install tools
|
|
run: pip install pytest ruff
|
|
|
|
# The real Module 14 checks still run — a self-hosted runner has to actually do the work.
|
|
- name: Lint
|
|
run: ruff check .
|
|
|
|
- name: Test
|
|
run: pytest -q
|
|
|
|
# The point of THIS workflow: make the runner identify itself.
|
|
- name: Where did this run?
|
|
shell: bash
|
|
run: |
|
|
echo "=== runner identity ==="
|
|
echo "hostname : $(hostname)"
|
|
echo "os : $(uname -a)"
|
|
echo "user : $(whoami)"
|
|
echo "workdir : $(pwd)"
|
|
echo
|
|
echo "=== ephemeral? (does junk from a previous run survive?) ==="
|
|
MARK="$HOME/.module19_ran_before"
|
|
if [ -f "$MARK" ]; then
|
|
echo "FOUND a marker from a PREVIOUS run at $MARK"
|
|
echo " -> this machine is PERSISTENT (not a fresh throwaway). Expect a self-hosted runner."
|
|
else
|
|
echo "No marker found. Either this is a fresh machine (hosted) or the first run here."
|
|
fi
|
|
date > "$MARK" 2>/dev/null && echo "(left a marker for next time)" || echo "(could not write a marker)"
|
|
echo
|
|
echo "=== can this runner reach the public internet? ==="
|
|
if curl -fsS -m 5 https://example.com >/dev/null 2>&1; then
|
|
echo "YES — outbound internet works from here."
|
|
else
|
|
echo "NO — no outbound internet (could be an air-gapped / isolated runner)."
|
|
fi
|
|
echo
|
|
echo "Now ask: is this machine MINE, and what else can it reach? (see inspect-runner.sh)"
|