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
翻訳待ち
No updates detected yet. GitHub releases will appear here.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Live portal for the Shellfish Hardening & Organismal Resilience Experimentation Center (Roberts Lab, UW). Published at https://robertslab.github.io/shore-line/.
| Widget | Source | Refresh |
|---|---|---|
| Live Tankcams | gannet v1_web/webcam/latest.jpg and v1_web/webcam_02/latest.jpg (Last-Modified header), plus live HLS video from v1_web/webcam_03/stream.m3u8 (native HLS, else hls.js; hls.js needs gannet to send CORS headers) → data/webcam.json | site rebuild every ~10 min; page re-polls every 60 s |
| Puget Sound water temp | NOAA CO-OPS (Tacoma 9446484, fallback Port Townsend) → data/field-water.json + assets/water-banner.svg | every rebuild |
| Water-quality reports + per-tank readings | genefish RSS (Jesse Lowe) → data/reports.json | every rebuild |
| Facility temperatures | data/tanks.json (setpoint); one card, the Seneye Tank (Left Blue), live from a seneye → seneye-data branch → data/seneye.json; plus one card per DS18B20 probe on the ESP32 hubs, from Gannet's raw CSVs (SHORE_temps/data/raw/<hub>/) → data/shore-temps.json (names in tanks.json → probes) | seneye every 15 min; probes every rebuild |
| Research from SHORE | data/research.json (hand-curated) | — |
A static site (index.html, css/, js/) with no build step.
.github/workflows/site.yml runs every 10 minutes. It fetches the live sources with the stdlib-only scripts in scripts/, writes the results into _site/, and deploys to GitHub Pages. Fetched data is not committed. If a source is down, the script republishes the copy that is currently live and marks it with an error, and the status dot for that feed turns amber or red.
The Seneye Web Server sits on a private UW address (172.25.149.26), which GitHub can't reach. So scripts/collect_seneye.py runs on a machine inside the network. It decodes the SWS WebSocket state, which has no JSON API, and keeps a 14-day series. scripts/seneye_publish.sh force-pushes that file as a single commit on the seneye-data branch. The site build mirrors it from the SENEYE_URL repo variable.
/tmp/shore-seneye.log.scripts/install_seneye_agent.sh
launchctl unload ~/Library/LaunchAgents/com.robertslab.shore-seneye.plistseneye_publish.sh from cron there. Alternatively, write the JSON to a web-served path and point SENEYE_URL at it.null for those instead.items in data/research.json (featured: true puts it in the top cards, max 3). Remove the placeholder entry once there's a real one.data/tanks.json. Set status to anything other than placeholder and fill latest / series when a logger feed exists.WEBCAM_URL, REPORTS_FEED, SITE_LABEL.python3 scripts/update_webcam.py && python3 scripts/update_reports.py && python3 scripts/update_field_water.py
python3 -m http.server 8320
Then open http://localhost:8320. update_field_water.py --demo uses synthetic data when you have no network.
See PLAN.md for the roadmap.