ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Next.js (App Router) + TypeScript + Tailwind + shadcn/ui + Supabase — TYT/AYT
exam-coaching platform for student/parent/coach/admin roles. Runs entirely
against a local Supabase (Docker), not the cloud project.
supabase start prints a local ANON_KEY — put it, with the local API URL,
into .env.local (see .env.local.example):檢視完整 README ↗Next.js (App Router) + TypeScript + Tailwind + shadcn/ui + Supabase — TYT/AYT exam-coaching platform for student/parent/coach/admin roles. Runs entirely against a local Supabase (Docker), not the cloud project.
pnpm install
npx supabase start # starts local Postgres/Auth/Storage in Docker
pnpm dev
supabase start prints a local ANON_KEY — put it, with the local API URL,
into .env.local (see .env.local.example):
NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
NEXT_PUBLIC_SUPABASE_ANON_KEY=<anon key from `supabase start`>
Migrations and supabase/seed.sql apply automatically on supabase start /
supabase db reset. The seed creates a standing local admin account:
[email protected] / LocalAdmin123! — sign in at /login?role=admin, no
sign-up needed. Supabase Studio (table/data browser) is at
http://127.0.0.1:54323.
app/ — one folder per role (student/, parent/, coach/, admin/),
gated by proxy.ts based on the signed-in user's profiles.role. / is
the panel picker / entry page. Admins additionally get an exception in
proxy.ts to browse every panel, with a switcher bar (rendered from each
panel's layout.tsx) to jump between them without logging out.components/ui/ — shadcn/ui primitives (hand-installed; the CLI's init
endpoint is unreachable from this sandbox, so components are added by
copying source directly — same result as the CLI produces).lib/supabase/ — browser, server, and proxy (middleware) Supabase clients.lib/curriculum/ — generated TYT/AYT course data (see below). Don't hand-edit
the JSON.supabase/migrations/ — SQL schema: profiles (role-tagged user table,
shared across all four roles) plus the persisted student-data tables
(task_completions, student_resources, student_resource_progress,
paragraf_problem_entries), all RLS-scoped to their owning student.supabase/seed.sql — recreates the local admin account on every reset.supabase/curriculum-source/ — the source .xlsx workbooks the curriculum
is generated from.lib/curriculum/*.json is generated from the three official curriculum
workbooks in supabase/curriculum-source/ (Sayısal / Eşit Ağırlık / Sözel).
Re-run after the source workbooks change:
pnpm run parse-curriculum
Ödevler, Kaynak Takibi, and Paragraf/Problem Takibi read/write real Supabase
tables via Server Components + Server Actions (actions.ts next to each
page) — not local React state. Each student only ever sees their own rows
(RLS student_id = auth.uid()). Coach/parent/admin views into that data,
homework assignment, and file-upload storage for excuse photos are not built
yet — see the project's v1.1 plan for what's intentionally deferred.