Synaplan
開源 AI 平台,供企業使用:自行託管的 AI 代理、符合 GDPR 的聊天機器人小工具、RAG 知識庫、WhatsApp 與 Outlook AI、MCP、多模型路由。Docker、Kubernetes 或託管於 Germ
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Employee-initiated exit tracking and verification
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗An employee-initiated shared exit tracker for employees leaving small and mid-sized companies that still manage offboarding manually through email, WhatsApp, spreadsheets and HR follow-ups.
The employee tracks each exit item, submits evidence, and sends HR a private verification link. The verifier approves, requests more information, or rejects — no HR account needed. The employee always sees what has been validated and what is overdue.
ExitProof does not provide legal advice and does not calculate F&F entitlement. A verification link proves possession of the link, not the identity of the person who used it.
Next.js 16 (App Router) · TypeScript · Tailwind CSS 4 · Supabase (Auth email + password, Postgres, Storage) · Vercel
cp .env.example .env.local # fill in Supabase values; keep NEXT_PUBLIC_SITE_URL=http://localhost:3000
npm install
npm run dev # http://localhost:3000
Database: run each file in supabase/migrations/ once in the Supabase SQL Editor, in filename order, one file per run (each run must succeed before the next): the initial schema, then the request-workflow enums, then the request workflow (tables, RLS, functions, private evidence and hr-documents buckets and storage policies). In Supabase Auth, enable Email sign-ups and turn Confirm email off.
For local development against a separate Supabase project, put its three values in .env.development.local (git-ignored). npm run dev reads it in preference to .env.local; next build / next start do not.
Import the repository with the default Next.js settings and set these environment variables (Production):
| Variable | Kind |
|---|---|
NEXT_PUBLIC_SUPABASE_URL | config |
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY | config (safe in the browser) |
NEXT_PUBLIC_SITE_URL | config: the production origin, e.g. https://<project>.vercel.app (no trailing slash) |
SUPABASE_SECRET_KEY | secret — server-only, never prefix with NEXT_PUBLIC_ |
NEXT_PUBLIC_* values are inlined at build time, so redeploy after changing them. If NEXT_PUBLIC_SITE_URL is unset on Vercel, verification links fall back to the project's production domain.
See docs/PLAN.md for the approved plan, data model and acceptance criteria.