ChengOS
Rust 엔진 기반 시각화 AI 데이터 처리 및 에이전트 워크플로우 시스템
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Serverless climate monitoring network for Cồn Hô — public climate information platform, citizen science initiative, and eco-tourism support system.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Environmental monitoring platform for a farming community on Cồn Hô, an island in Vĩnh Long, Vietnam. Originally built as "Eco-Sense Cồn Hô" — that name persists in some technical identifiers (npm workspace scopes) and is not renamed without a deliberate migration.
For the real, current, source-verified architecture — station topology,
what's live vs. not yet deployed, whether GCP is required — see
docs/ARCHITECTURE.md. This file is a short
front door only; it is not the source of truth for architecture claims.
The project presentation is a 20-slide Canva deck, HORIZON - FROGSLEAP VIETNAM, shared alongside the website: canva.link/frbq9egh4e8uuu7.
Three physical field devices (a water station, a soil station, and a
gateway) relay signed telemetry to a Supabase Edge Function, which
validates and stores it in Postgres. A Next.js PWA reads that data for a
public dashboard, per-station pages, a community field-report flow, and a
password-gated admin console. Full handbook: docs/README.md.
.
├── apps/web/ Next.js 15 PWA (public + admin)
├── services/edge-ingestion/ Telemetry validation logic + Deno edge function source
├── firmware/esp32-node/ ESP32 firmware (station1 / station2 / gateway)
├── infra/supabase/ SQL migrations, seed data, deploy/verify scripts
└── docs/ Product handbook — start at docs/README.md
npm install
npm run check # typecheck all workspaces
npm run test # edge-ingestion contract tests (mocked, no network)
npm run test:web # web app unit tests (mocked, no network)
npm run dashboard # start the Next.js app at http://localhost:4173
npm run simulator and npm run mock:ingest generate synthetic telemetry
for local UI development. Correction (Phase G): an earlier version of
this README claimed these write to a live Supabase project if pointed at
one — that was checked against the source and found to be wrong. Both
scripts hardcode MockDb (services/edge-ingestion/src/mockDb.ts) with
no network code path at all; simulator.ts only writes local files under
apps/web/mock/*.json, mock_ingest.ts only logs to the console. Neither
can write to a real Supabase project regardless of environment variables.
| Command | Tier | Writes to live Supabase? |
|---|---|---|
npm run check, npm run lint | Static analysis | No |
npm run test, npm run test:web | Unit / mocked | No — no network calls |
npm run simulator, npm run mock:ingest | Synthetic telemetry generator | No — MockDb only, no network code path exists |
npm run test:rls | Mocked unless RUN_RLS_TESTS=1 | Yes if enabled — creates real throwaway users/assignments |
npm run test:integration, npm run test:all | Live integration | Yes if LIVE_SUPABASE_INTEGRATION=1 — POSTs real signed telemetry through edge-ingest |
test:rls and test:integration/test:all are the only commands that
require caution — both need deliberately-set env vars and should not be
run against this project's live Supabase instance without a specific
reason. .github/workflows/ci-live-smoke.yml runs both on a weekly cron
if its GitHub secrets are configured — see docs/ARCHITECTURE.md for the
current status of that workflow.
NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
SUPABASE_SERVICE_ROLE_KEY=
See apps/web/README.md for the full list including
admin-auth variables.
Backend and frontend are live against a real Supabase project (migrations
27 tracked migrations applied, including the additive 024/025 gateway and
timezone follow-ups). Three GitHub Actions workflows
exist under .github/workflows/ (validation on every PR/push, a weekly
live-integration smoke test, and a tag-triggered release/deploy pipeline)
— and the current token-authenticated gateway route retains real observation
envelopes and promotes their nested water/soil readings. Physical installation
and field calibration are not established by the repository alone.
See docs/ARCHITECTURE.md
for the exact current-vs-future boundary, and
docs/EDGE_INGEST_READINESS.md for what's
blocking a real deployment.
All rights reserved unless otherwise specified.