Busabase
Busabase is an open-source (MIT) database and workspace for AI agents — data, docs, skills, and apps in one place. Run it locally, self-host it inside your network, or use Busabase Cloud, and turn age
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證適用於 K-12 教育的現代化數據堆疊。
AI 翻譯
A modern data stack for K-12 education
正在載入完整 README。 以下為已儲存的摘錄。
Next-gen data orchestration for KIPP TEAM & Family Schools
Teamster is the data engineering platform powering analytics and reporting
across KIPP Newark, Camden, Miami, and Paterson. It ingests data from 30+ source
systems, transforms it through dbt, and delivers it to Tableau, Google Sheets,
PowerSchool, and other consumers — all orchestrated by Dagster.檢視完整 README ↗Teamster is the data engineering platform powering analytics and reporting across KIPP Newark, Camden, Miami, and Paterson. It ingests data from 30+ source systems, transforms it through dbt, and delivers it to Tableau, Google Sheets, PowerSchool, and other consumers — all orchestrated by Dagster.
KIPP's data infrastructure was previously a patchwork of Python scripts, cron jobs, stored procedures, Fivetran, and Selenium automation spread across multiple databases. Synchronous scheduling meant a slow pull from one system would cascade into downstream failures. A single data engineer spent more time firefighting than building.
Teamster replaced all of it with a unified, asset-based platform. The results:
"The visibility into the pipelines is a game changer. We know as soon as something fails and why."
Read the full story in the Dagster case study.
New to the project? Start here:
| Topic | Description |
|---|---|
| Automations | All schedules and sensors across every code location |
| Automation Conditions | How asset auto-materialization works |
| Adding an Integration | Step-by-step guide for new data sources |
| dbt Conventions | Model naming, contracts, and testing standards |
| IO Managers | How intermediate data is stored in GCS |
| Fiscal Year & Partitioning | Partition strategy for historical loads |
| Topic | Description |
|---|---|
| Dagster Guide | Tableau scheduling, backfills, branch deployments |
| Google Sheets & Forms | Adding and updating Google Sheets sources |
| Troubleshooting: Dagster | Pipeline failures, partitions, unsynced views |
| Troubleshooting: dbt | Contract violations, compilation errors, test failures |
| Troubleshooting: VS Code | Interpreter, secrets, Trunk, container issues |