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.