Repository navigation
FAQ
No. It is informational software only — not a medical device and not a substitute for a clinician. See NOTICE.
Operators are responsible for third-party terms of service and local law. Prefer caching, avoid refresh=1 hammering, and use SKIP_PLAYWRIGHT=1 for light local/dev runs. The authors assume no liability for scraping.
Never in git. Use .env files (gitignored) and docs/API_KEYS.local.md (gitignored). Templates: .env.example, docs/API_KEYS.local.md.example. Guide: docs/API_KEYS.md.
Fresh scrapes run in the background so they don't block gunicorn workers. Clients must poll the job, then re-request. Old clients that don't handle 202 need updating — ship API + web + APK together.
.github/workflows/deploy-*.yml deploy MedMx Labs Azure on push to main. Your fork won't have those secrets — expected. Don't put real cloud keys in a public fork.
Not as a public issue. Use a private advisory — SECURITY.md.
docs/ in the repo is the source of truth (versioned with code). This wiki is a friendly index. Prefer editing docs/ for technical detail.