Sabaki Guide
Replit Project Evidence Setup In Sabaki
How to connect Replit app details, repository imports, and deployment probes as Sabaki evidence.
Replit project evidence sync is the Sabaki workflow for storing Replit app configuration, linked repositories, and optional deployment probe results as evidence items.
Key Takeaways
- Replit is evidence-oriented in Sabaki and does not currently write KPI rows.
- Repository imports become workflow handoff evidence.
- Optional health or status URLs can become deployment probe evidence.
How To Sync Replit Evidence
- Collect Replit app detailsPrepare the Repl ID, app URL, deployment URL, repository links, and optional health URL.
- Connect Replit in SabakiOpen Apps, choose Replit, and save the app configuration.
- Run Sync NowSync repository and deployment evidence from the saved configuration.
- Review probe resultsIf a health URL is configured, check whether the deployment probe responded successfully.
- Update after deployment changesRefresh the connection when URLs, repositories, or health endpoints change.
Quick Comparison
| Synced Item | Source | Sabaki Use |
|---|---|---|
| Repository handoff | Configured repository imports | Source-backed product workflow evidence |
| Deployment probe | Health or status URL | Runtime availability evidence |
| Sync cursor | Repository count and probe state | Connection sync status |
Frequently Asked Questions
Does Replit sync KPIs?
No. Replit currently syncs project and deployment evidence rather than KPI snapshots.
Do I need a health URL?
No. A health or status URL is optional, but adding one lets Sabaki preserve deployment probe evidence.
What happens if the probe fails?
Sabaki stores the probe result as evidence so users can inspect the response status and payload.
When should I update the Replit connection?
Update it when the app URL, deployment URL, repository list, or health endpoint changes.