최근 완료된 8시간 회차 사이 GitHub 스타 증가량 순
Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기A Cricket Prediction Platform
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
SightScreen
A Cricket Prediction Platform
See SPEC.md for the full build specification.
1. Copy api/.env.example to api/.env and web/.env.local.example to web/.env.local,
then fill in real values (never commit these — both patterns are gitignored).
2. Python service: pip install -e "./api[dev]"
3. Web app: cd web && npm install
Two Supabase API keys matter here, and mixing them up is the most common way to
accidentally leak data:README 전문 보기 ↗A Cricket Prediction Platform
See SPEC.md for the full build specification.
api/.env.example to api/.env and web/.env.local.example to web/.env.local,
then fill in real values (never commit these — both patterns are gitignored).pip install -e "./api[dev]"cd web && npm installFour processes, none of which needs the others to start first. Ports are 5433 (Postgres), 8000 (agent tools), 3000 (web).
# 1. Postgres - the training corpus and the agent's replica
docker compose up -d
# 2. Migrations, to BOTH databases (local + Supabase). Idempotent.
python supabase/apply_migrations.py
# 3. Agent tool endpoints (five routes under /agent)
cd api && ../api/.venv/Scripts/python.exe -m agent_tools.serve
# 4. Web app, including /ask
cd web && npm run dev
Step 3 refuses to start without AGENT_SQL_ROLE_DB_URL, because the
alternative is four tools returning 503 while get_player_form answers
normally - which reads as a broken agent rather than a missing variable.
A separate database (cricket_agent_replica) holding a projection of the
corpus, read through five views by a role with no table grants (SPEC.md
§2.1, §10.3). Build or rebuild it with one command - about five minutes for
3.78M deliveries:
.\scripts\setup-replica.ps1 "postgresql://postgres:postgres@localhost:5433/cricket_agent_replica?sslmode=disable"
It prints an AGENT_SQL_ROLE_DB_URL line once and writes it nowhere. Put
that in api/.env. Re-running rotates the password, so re-paste it.
--verify proves layers 1 and 3 against the real database rather than
asserting them, and fails on an unstamped replica - see
agent_tools/replica.py.
/ask is password-gated because it calls a paid API. Set in
web/.env.local:
| variable | what |
|---|---|
ASK_PASSWORD | the shared password a visitor types once |
ASK_SESSION_SECRET | HMAC key for the session cookie; any long random string |
ASK_DAILY_COST_CAP | dollars per UTC day before /ask pauses (default 2) |
AGENT_TOOL_SHARED_SECRET must be identical in api/.env and
web/.env.local. When it is not, every tool call returns 401 while the
password gate, the page and the model call all work - so it reads as a
broken agent. tests/test_shared_secret_parity.py compares them.
cd api && ../api/.venv/Scripts/python.exe -m pytest ../tests -q # ~470, 13 min
cd web && npm test # ~84, seconds
Run the Python suite from api/ - config.py resolves its .env
relative to the working directory, and from the repo root it fails on
SUPABASE_URL: Field required.
The deterministic half runs in CI on every push. The model-calling half costs money and is a deliberate command:
cd api
../api/.venv/Scripts/python.exe -m agent_eval.runner --status # is a paid job running?
../api/.venv/Scripts/python.exe -m agent_eval.runner --all # full pass, ~$1.15, ~15 min
../api/.venv/Scripts/python.exe -m agent_eval.runner --prove citation
Results land in api/data/agent_eval/results.json with the model id, both
fingerprints, the rates they were costed at, and complete. They are written
after every conversation, so a crash costs one conversation rather than
the pass. CI fails when either fingerprint no longer matches the committed
results - which enforces that the paid half was re-run, without CI ever
calling a model.
--status reads a heartbeat file rather than the process table. Liveness is
the age of that file: a buffered pipe and ps both lied about a running job
once each, and the second time it cost a duplicate paid run.
Two Supabase API keys matter here, and mixing them up is the most common way to accidentally leak data:
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY is public by design. It's safe in the browser
bundle — row-level security (RLS) policies on the Supabase tables are what actually
protect the data, not secrecy of this key.SUPABASE_SECRET_KEY bypasses RLS entirely. It belongs only in the Python service
and in server-side Next.js route handlers — never under a NEXT_PUBLIC_ prefix or
anywhere reachable from the browser.| Variable | Purpose | Where to get it | Deploy target |
|---|---|---|---|
LOCAL_DATABASE_URL | Docker-compose training Postgres connection string (port 5433, sslmode=disable) | docker-compose.yml | Local only |
CRICSHEET_DATA_DIR | Cache dir for downloaded/extracted Cricsheet JSON | Any local path you choose | Local only |
SUPABASE_URL | Supabase project REST URL | Supabase dashboard → Project Settings → API | Railway |
SUPABASE_SECRET_KEY | Server-side key, bypasses RLS | Supabase dashboard → API keys | Railway, Vercel (server-only) |
SUPABASE_SESSION_POOLER_URL | Supavisor session-mode pooler (port 5432) | Supabase dashboard → Connect → Session pooler | Railway (live worker, FastAPI, migrations) |
SUPABASE_TRANSACTION_POOLER_URL | Supavisor transaction-mode pooler (port 6543) | Supabase dashboard → Connect → Transaction pooler | Vercel, anything serverless (Phase 2) |
AGENT_SQL_ROLE_DB_URL | Read-only Postgres role for the agent's SQL tool, its own role and password | Created by a migration (Phase 6) | Railway (Phase 6) |
AGENT_TOOL_SHARED_SECRET | Authenticates web → FastAPI tool calls | Generate any random secret | Railway, Vercel (Phase 6) |
ANTHROPIC_API_KEY | Scouting reports, match narratives, agent chat | console.anthropic.com | Railway, Vercel |
LIVE_API_PROVIDER | Which LiveClient implementation to load | One of cricketdata/sportmonks/roanuz | Railway (Phase 2) |
LIVE_API_KEY | Live provider credential | Chosen provider's dashboard | Railway (Phase 2) |
PORT | FastAPI bind port |
SUPABASE_URL and SUPABASE_SECRET_KEY are also needed as GitHub Actions secrets
(Settings → Secrets and variables → Actions) for calibration.yml/drift.yml, which read
and write Supabase's predictions/model_versions tables on a schedule.
SUPABASE_ACCESS_TOKEN is a separate GitHub Actions secret (not an env var used by the
app itself) — a personal access token from Supabase dashboard → Account → Access Tokens,
used only by ci.yml's web/lib/types.ts staleness check to call the Management API and
regenerate types for comparison. Never the same as SUPABASE_SECRET_KEY.
Never use a direct connection string (db.<ref>.supabase.co) anywhere in this project.
It resolves over IPv6 only and is unreachable from Railway or Docker's default bridge
network — it fails as a DNS error, not a connection error, which is confusing the first
time. Always copy pooler strings from the dashboard's Connect button rather than
assembling them by hand; the region prefix varies and the username is postgres.<PROJECT_REF>,
not bare postgres. See SPEC.md section 2.4. config.py fails fast at startup if either
mistake makes it into .env.
After filling in .env/.env.local, sanity-check that every Postgres host in api/.env
actually resolves, before finding out the hard way from a connection error:
Get-Content api\.env | ForEach-Object {
if ($_ -match '^(LOCAL_DATABASE_URL|SUPABASE_SESSION_POOLER_URL|SUPABASE_TRANSACTION_POOLER_URL|AGENT_SQL_ROLE_DB_URL)=(.+)$') {
$name = $Matches[1]
$raw = $Matches[2]
if ([string]::IsNullOrWhiteSpace($raw)) { return }
$uriHost = ([Uri]$raw).Host
$uriPort = ([Uri]$raw).Port
try {
$addrs = [System.Net.Dns]::GetHostAddresses($uriHost)
Write-Host ("{0,-32} {1}:{2} -> OK ({3})" -f $name, $uriHost, $uriPort, ($addrs -join ', '))
} catch {
Write-Host ("{0,-32} {1}:{2} -> FAILED to resolve" -f $name, $uriHost, $uriPort) -ForegroundColor Red
}
}
}
This only reads the host and port out of each URL — it never touches or prints the
username/password portion. A FAILED to resolve result on a Supabase URL almost always
means a direct connection string (db.<ref>.supabase.co) slipped in instead of a pooler
string.
Two Railway services, one Docker image, one repository. Vercel deploys web/;
Railway deploys api/. The always-on worker is a deliberate cost — a process
that polls every 15 seconds for four hours cannot run on serverless, and no
configuration makes it work (SPEC.md section 2.2).
| Service | SERVICE_ROLE | What it does |
|---|---|---|
api | api | FastAPI prediction service — GET /health, POST /predict/win-prob |
worker | worker | Always-on live poller (SPEC.md section 7.1), idling at 600s |
Both run python -m serving.entrypoint, which dispatches on SERVICE_ROLE.
One image because the two share ~100% of their dependencies; two services
because their lifecycles differ — the API is request-scoped and scalable, the
worker is a singleton whose per-match in-memory state two replicas would
corrupt.
Set every variable in the Railway dashboard. Nothing is committed; .env is
gitignored and excluded from the build context. LOCAL_DATABASE_URL must
NOT be set on Railway — a container that can see it refuses to start, by
design (SPEC.md section 2.1), and there is a test proving it does.
Publishing a model is a separate, deliberate step, not a side effect of training. A serving container pulls its artifact from a GitHub Release and verifies the bytes before loading them:
# 1. create a GitHub Release tagged with the model version and upload the .pkl
# 2. register it on Supabase (verifies the download and its sha256 first)
cd api/src
python -m models.publish_model_version winprob2-20260910 `
--url https://github.com/Aarav-Patel06/SightScreen/releases/download/winprob2-20260910/winprob2-20260910.pkl
The digest is appended to the stored URL as a #sha256= fragment, so the
location and the expected bytes cannot drift apart. If MODEL_VERSION
disagrees with Supabase's active row, the container refuses to start rather
than serving predictions that would be attributed to the wrong model.
To redeploy:
npx @railway/cli login
npx @railway/cli link # project "giving-comfort", environment "production"
npx @railway/cli up --service api
npx @railway/cli up --service worker
curl https://<your-api-service>.up.railway.app/health
/health reports what the process actually resolved rather than what it was
told — the pooler host, the resolved IP and address family, the loaded model's
sha256, and how many days ago the reference tables were synced. The address
family matters: a direct Supabase host resolves IPv6-only and is unreachable
from Railway, and it fails as a DNS error rather than a connection error
(SPEC.md section 2.4).
Two operational notes worth knowing before they bite:
supabase/SCHEMA.md), so a fortnight of not running it takes the worker
down deliberately rather than letting it serve stale features.Supabase project appears PAUSED and retries with backoff instead of
crash-looping. A genuine credentials failure is the one case that exits
immediately — retrying a wrong password forever is a silent outage.Historical training data is Cricsheet, openly licensed for non-commercial use — see their site for current licence terms.
| Usually auto-injected |
| Railway |
SERVICE_ROLE | Which process the container starts: api or worker | Set per Railway service; defaults to api | Railway |
MODEL_VERSION | The model this container is pinned to, e.g. winprob2-20260910 | Must match Supabase's active model_versions row | Railway |
MODEL_CACHE_DIR | Where the downloaded artifact is cached | Defaults to /app/artifacts in the image | Railway (optional) |
NEXT_PUBLIC_SUPABASE_URL | Public Supabase URL | Supabase dashboard → Project Settings → API | Vercel |
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY | Public key, safe in the browser | Supabase dashboard → API keys | Vercel |
API_BASE_URL | FastAPI service URL, for agent tool calls | Your Railway service URL | Vercel (Phase 6) |