learning_ai_common_plat/npmrc.template at 6f6e005114b3dea7b2bc2a759a685f4b0e781364 - learning_ai_common_plat - Gitea: Git with a cup of tea

bytelyst/learning_ai_common_plat

saravanakumardb1 610a59fdc3 feat(gitea): parameterize owner via GITEA_NPM_OWNER + add doctor/token helpers

Eliminates the three operational pain points hit in the last
owner-rename incident:

1. Owner-rename drift across 14 repos
   - npmrc.template now uses ${GITEA_NPM_OWNER:-learning_ai_user}
   - switch-network.sh exports GITEA_NPM_OWNER on shell start
   - Future renames are a one-line env change, not 14 git commits

2. Stale shell-env tokens (file rotated, env didn't)
   - scripts/gitea/token.sh: status|print|validate|rotate subcommands
   - 'eval "$(bash scripts/gitea/token.sh print --export)"' refreshes
     any shell without re-sourcing ~/.zshrc
   - rotate uses Gitea API + macOS Keychain for admin creds

3. No pre-deploy validation
   - scripts/gitea/doctor.sh: NETWORK + DNS + token consistency +
     registry HTTP 200 + optional package@version probe
   - Run before any deploy that needs @bytelyst/* from Gitea

2026-05-27 00:41:47 -07:00

6 lines

313 B

Plaintext

Raw Blame History

 @bytelyst:registry=http://${GITEA_NPM_HOST:-localhost}:3300/api/packages/${GITEA_NPM_OWNER:-learning_ai_user}/npm/
 //${GITEA_NPM_HOST:-localhost}:3300/api/packages/${GITEA_NPM_OWNER:-learning_ai_user}/npm/:_authToken=${GITEA_NPM_TOKEN}
 strict-ssl=false
 link-workspace-packages=true
 prefer-workspace-packages=true