ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Bilingual (English/Arabic) workspace for student training events, shared tasks and team coordination.
docs/)/api/ requests; every other address redirects to the website.The administrator account (ADMIN_EMAIL in wrangler.jsonc) is activated once, through a private setup link of the form login.html#setup=<token>. The server stores only the SHA-256 digest of that token, as the ADMIN_SETUP_TOKEN_HASH secret, and refuses a second activation. The browser removes the token from the address bar and sends it only to the API as a header. Never add the link or token to source, logs or documentation.
After activation, public signup stays closed. The administrator creates team accounts under Accounts & permissions, chooses roles, disables accounts and resets passwords. There is no email verification or email password recovery.
Passwords use salted scrypt (N=32768, r=8, p=3). The website uses bearer sessions stored per browser tab, so no third-party cookies are needed. Sessions are stored as SHA-256 hashes, expire after eight hours or one idle hour, and are invalidated by role/password/email changes or account deactivation. Writes require a CSRF token and a server-authorized role. Cross-origin requests are accepted only from FRONTEND_ORIGIN. Every signed-in role sees the same events, task instructions and assignments, and open pages refresh every 15 seconds.
npm run dev starts a local preview. Copy .env.example to .dev.vars for local settings.npm run build:pages regenerates docs/ from training-ui/ and scripts/pages-runtime.js. Commit and push to publish the website.npm run deploy builds and deploys the account server (requires npx wrangler login).npm run db:generate creates a migration after changing db/schema.ts; npm run db:migrate applies migrations to the production database.Document tracking stores manually supplied file links and approval state; it does not upload files.