nexus_github_check
Val Town is a collaborative website to build and scale JavaScript apps.
Deploy APIs, crons, & store data – all from the browser, and deployed in milliseconds.
Viewing readonly version of main branch: v4View latest version
A Val Town microservice that monitors the Ryizome GitHub repository and reports commit activity to the DDCT Nexus monitoring system.
This service fetches commit data from the GitHub API and tracks:
- Last commit timestamp
- Number of commits in the last 24 hours
- Number of commits in the last 48 hours
- Number of commits in the last 7 days
- Last commit author, message, and SHA
The data is reported to the nexus service and appears in the daily status report sent via Telegram.
GITHUB_PAT (required): GitHub Personal Access Token with repository read access
To create a GitHub PAT:
- Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic)
- Generate new token with
reposcope (or use fine-grained token withContents: Read-only) - Add the token to Val Town environment variables
Recommended: Daily execution (e.g., midnight UTC)
Set in Val Town dashboard when creating the interval val.
- Create a new Val in Val Town
- Set as interval type
- Add
GITHUB_PATenvironment variable - Copy code from
main.tsx - Set schedule to daily
- Save and test
Or use vt CLI:
cd nexus_github_check vt push
The service reports to nexus with service name RyizomeGitHub.
Check the daily report in Telegram for status:
RyizomeGitHub: 🟩 (OK)
📊 3/5/18 commits (24h/48h/7d)
⏱️ Last: 2h ago by aeone
💬 "Update nexus tracking system"
If the GitHub API check fails:
- Error is logged to console
- ERROR status is reported to nexus
- Daily report shows:
RyizomeGitHub: 🟥 (ERROR)
Common errors:
- Missing or invalid
GITHUB_PAT - GitHub API rate limit (unlikely with daily checks)
- Network connectivity issues
- Repository access issues
node:crypto- For checksum generation- Val Town SQLite - Used by nexus for data storage
- GitHub REST API v3