Synaplan
开源 AI 软件平台,面向企业:自托管 AI 代理,符合 GDPR 的聊天机器人小部件,RAG 知识库,WhatsApp 与 Outlook AI,MCP,多模型路由。支持 Docker、Kubernetes 或在 Germ 托管。
AI 翻译
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
Next.js (App Router, TypeScript) + Supabase + Vercel.
• Framework: Next.js 15 (App Router) + TypeScript + Tailwind CSS
• Database / Auth: Supabase (@supabase/ssr)
• Hosting: Vercel
• Package manager: npm
Two separate Supabase projects keep staging data fully isolated from
production. The same SQL migrations are applied to both to keep schemas identical.
1. Copy env template and fill in your staging Supabase keys:查看完整 README ↗Next.js (App Router, TypeScript) + Supabase + Vercel.
@supabase/ssr)| Environment | Git branch | Vercel target | Supabase project |
|---|---|---|---|
| Local dev | any | — | fusion-studio-staging (or local Supabase) |
| Staging | staging | Preview | fusion-studio-staging |
| Production | main | Production | fusion-studio-prod |
Two separate Supabase projects keep staging data fully isolated from production. The same SQL migrations are applied to both to keep schemas identical.
cp .env.example .env.local
# then edit .env.local
npm run dev
App runs at http://localhost:3000| Variable | Where | Notes |
|---|---|---|
NEXT_PUBLIC_SUPABASE_URL | client + server | Project URL |
NEXT_PUBLIC_SUPABASE_ANON_KEY | client + server | Public anon key |
SUPABASE_SERVICE_ROLE_KEY | server only | Never expose to the browser |
NEXT_PUBLIC_SITE_URL | client + server | Base URL for redirects |
import { createClient } from "@/lib/supabase/client"import { createClient } from "@/lib/supabase/server"src/proxy.ts (this Next.js version renamed the middleware convention to proxy).supabase migration new <name> # create a migration
supabase db reset # rebuild LOCAL db from migrations
supabase link --project-ref <ref> # link a remote project
supabase db push # apply migrations to the linked remote project
Apply the same migrations to staging first, then production.
staging → Vercel Preview deploy (uses staging Supabase env vars).main → Vercel Production deploy (uses production Supabase env vars).