learning_ai_common_plat

bytelyst/learning_ai_common_plat

Fork 0

Commit Graph

Author	SHA1	Message	Date
saravanakumardb1	7e1a2ad660	feat(gitea): add-host-runner.sh for multi-runner CI parallelism - scripts/gitea/add-host-runner.sh: stand up Nth independent host-mode runner as its own launchd service (separate config/.runner/workdir, shared runner.env token, admin-API registration token, idempotent reload) - GITEA_VM_SETUP.md 11.5: document multi-runner setup, fleet list/prune, and removal; 3 runners x capacity 2 ~= 6 parallel slots (verified) Live fleet: learning-ai-mac (brew) + 2 added runners, all online; stale offline registrations pruned.	2026-05-28 18:31:57 -07:00
saravanakumardb1	3224199894	feat(gitea): reproducible Actions runner registration + harden runner config - add scripts/gitea/register-runner.sh (idempotent register, host/docker modes, capacity arg, admin-API registration token, --force re-register) - GITEA_VM_SETUP.md Step 11: runner install/register, host-vs-docker tradeoffs, token externalization (env_file), concurrency (capacity), token rotation, end-to-end CI verification - document runner registration + secrets in persist/ephemeral table Live runner hardened separately: capacity 1->2, GITEA_NPM_TOKEN moved from inline config.yaml to chmod-600 runner.env via env_file.	2026-05-28 18:05:55 -07:00
saravanakumardb1	925c081ce3	docs(runbooks): GITEA_VM_SETUP.md — step-by-step cloud VM wiring Copy-pasteable runbook for the case where: - VM is already provisioned - Gitea is already installed and running on :3300 - Repos are already cloned on the VM - User needs to wire admin + npm-user + token + laptop end-to-end 10 numbered steps with expected outputs and troubleshooting: 1. Create Gitea admin user (idempotent skip if exists) 2. Create npm owner user (learning_ai_user) 3. Mint npm-scoped token via API 4. Write token to ~/.gitea_npm_token_home on laptop 5. Update ~/.gitea_vm_host with VM hostname 6. Pre-flight verification via doctor.sh (expects 404 on probe) 7. Publish @bytelyst/* via publish-local-packages.sh 8. End-to-end verification (re-run doctor + smoke-test pnpm install) 9. Optional: backfill historical versions 10. Persist environment in ~/.zshrc Includes troubleshooting table, persistence map (what survives VM reboot vs rebuild), and Azure NSG/firewall guidance. Companion to scripts/gitea/{bootstrap-vm,doctor,token}.sh.	2026-05-27 03:46:09 -07:00

Author

SHA1

Message

Date

saravanakumardb1

7e1a2ad660

feat(gitea): add-host-runner.sh for multi-runner CI parallelism

- scripts/gitea/add-host-runner.sh: stand up Nth independent host-mode runner
  as its own launchd service (separate config/.runner/workdir, shared
  runner.env token, admin-API registration token, idempotent reload)
- GITEA_VM_SETUP.md 11.5: document multi-runner setup, fleet list/prune,
  and removal; 3 runners x capacity 2 ~= 6 parallel slots (verified)

Live fleet: learning-ai-mac (brew) + 2 added runners, all online; stale
offline registrations pruned.

2026-05-28 18:31:57 -07:00

saravanakumardb1

3224199894

feat(gitea): reproducible Actions runner registration + harden runner config

- add scripts/gitea/register-runner.sh (idempotent register, host/docker modes,
  capacity arg, admin-API registration token, --force re-register)
- GITEA_VM_SETUP.md Step 11: runner install/register, host-vs-docker tradeoffs,
  token externalization (env_file), concurrency (capacity), token rotation,
  end-to-end CI verification
- document runner registration + secrets in persist/ephemeral table

Live runner hardened separately: capacity 1->2, GITEA_NPM_TOKEN moved from
inline config.yaml to chmod-600 runner.env via env_file.

2026-05-28 18:05:55 -07:00

saravanakumardb1

925c081ce3

docs(runbooks): GITEA_VM_SETUP.md — step-by-step cloud VM wiring

Copy-pasteable runbook for the case where:
- VM is already provisioned
- Gitea is already installed and running on :3300
- Repos are already cloned on the VM
- User needs to wire admin + npm-user + token + laptop end-to-end

10 numbered steps with expected outputs and troubleshooting:
  1. Create Gitea admin user (idempotent skip if exists)
  2. Create npm owner user (learning_ai_user)
  3. Mint npm-scoped token via API
  4. Write token to ~/.gitea_npm_token_home on laptop
  5. Update ~/.gitea_vm_host with VM hostname
  6. Pre-flight verification via doctor.sh (expects 404 on probe)
  7. Publish @bytelyst/* via publish-local-packages.sh
  8. End-to-end verification (re-run doctor + smoke-test pnpm install)
  9. Optional: backfill historical versions
  10. Persist environment in ~/.zshrc

Includes troubleshooting table, persistence map (what survives VM reboot
vs rebuild), and Azure NSG/firewall guidance.

Companion to scripts/gitea/{bootstrap-vm,doctor,token}.sh.

2026-05-27 03:46:09 -07:00

3 Commits