Migration — Local Bot to Second PC

Goal: move the local Hermes bot (@Sportstlm_local_bot, currently DESKTOP-9LG2O7T) onto a 24/7 second PC, so the overnight scrapes (1am–10am) run regardless of the current desktop being asleep. Keep it to two bots: local (second PC) + VPS supervisor.

What migrates

Item Source (current desktop) Notes
Hermes config ~/AppData/Local/hermes/config.yaml settings (no secrets)
Secrets ~/AppData/Local/hermes/.env API keys + Telegram bot token — keep private
Credentials ~/AppData/Local/hermes/auth.json OAuth/credential pools
Skills ~/AppData/Local/hermes/skills/ 16 skills
Memory ~/AppData/Local/hermes/memories/ (MEMORY.md, USER.md) my persistent memory
SSH key ~/.ssh/sportstlm_vps (+ .pub) for scp → VPS pushes
GitHub auth gh auth (account investconfig-spec) for git push auto-commit
Scrape modules C:\SNOOKER, C:\BADMINTON, C:\TENNIS, C:\UFC, C:\GHY, racing the headed-Chrome scrapers
Task Scheduler jobs 9 local jobs reschedule to 1am–10am window

Steps (on the second PC)

  1. Install Hermes — run the installer, then hermes setup (pick the same model/provider).
  2. Copy the files above to the same paths on the second PC (.env + auth.json contain secrets — transfer privately, don't paste into chat).
  3. Copy the SSH key to ~/.ssh/ and chmod 600 sportstlm_vps.
  4. gh auth login as investconfig-spec (for auto-commit pushes).
  5. Point the Telegram bot — the .env already carries the @Sportstlm_local_bot token, so it re-homes automatically.
  6. Move the scrape modules + Task Scheduler (reschedule the 04:00–07:30 jobs into 1am–10am).
  7. hermes gateway start then hermes doctor to verify.
  8. Stop the gateway on the old desktop (avoid two instances of the same bot).

Result