Synaplan
开源 AI 软件平台,面向企业:自托管 AI 代理,符合 GDPR 的聊天机器人小部件,RAG 知识库,WhatsApp 与 Outlook AI,MCP,多模型路由。支持 Docker、Kubernetes 或在 Germ 托管。
AI 翻译
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
LawIntake is a client-intake and matter-management workspace for real estate law firms. It
combines guided intake, matter details, documents, AML workflows, and a client portal in one
Next.js application.
Install dependencies and start the development server:
Open http://localhost:3000.
Environment setup and database instructions are available in
docs/dev-setup.md.查看完整 README ↗LawIntake is a client-intake and matter-management workspace for real estate law firms. It combines guided intake, matter details, documents, AML workflows, and a client portal in one Next.js application.
Project site · Live application · Interactive demo
The interactive demo is the unauthenticated browser sandbox at /demo (no login, fictional
data in the browser). See docs/public-demo-sandbox.md. A legacy
Supabase is_demo_firm tenant is quarantined and is not the public prospect path.
Install dependencies and start the development server:
npm install
npm run dev
Open http://localhost:3000.
Useful checks:
npm run type-check
npm test
npm run check:compliance
Environment setup and database instructions are available in
docs/dev-setup.md.
The marketing landing files at the repository root (index.html, styles.css, script.js) remain
available for the existing Pages site, including the static Insights pages under insights/.
The Next.js app can also be built as a static export for
project Pages under the repository base path /intake-app.
/intake-app)GitHub Pages has no Node server, so export mode is opt-in and must not be used for Vercel:
npm run build:github-pages
This sets GITHUB_PAGES=true, which configures next.config.js with:
| Setting | Value | Why |
|---|---|---|
output | 'export' | Emit static HTML/CSS/JS into ./out |
basePath / assetPrefix | /intake-app | Match https://tommyjackson85.github.io/intake-app/ |
trailingSlash | true | Emit …/demo/index.html so Pages serves folder URLs |
images.unoptimized | true | Image Optimization API is unavailable on static hosts |
Vercel / npm run build leave GITHUB_PAGES unset, so those deployments keep root paths, server
headers, and the normal Next server output.
Publish the generated ./out directory as the GitHub Pages artifact (or copy it into your Pages
publishing folder). Client navigation via next/link and bundled assets include the /intake-app
prefix automatically when built this way.
Not included in the static export (stashed only for that build, then restored):
app/api/** route handlers and app/auth/logoutapp/auth/post-login (force-dynamic) and app/auth/signup (Server Action)app/dashboard/** (server/cookie-backed product UI)generateStaticParams: /demo/portal/[token],
/demo/intake/[token], /demo/fincen-cert/[token], /intake/[token]proxy.ts (request-time middleware replacement; unsupported for export)/demo/matters/[id] is included in the static export: generateStaticParams emits one page
per seeded demo matter file_id.
Those capabilities remain on Vercel. Hardcoded absolute <a href="/…"> strings (not next/link)
are not rewritten by basePath; prefer next/link for in-app navigation.