Lalabase
Tickets, Doku, Zeiterfassung und Kundengespräche an einem Ort, durchsuchbar per KI. Für Softwarefirmen mit Kundenprojekten. Open Source: auf deinem eigenen Server oder in unserer Cloud in Deutschland.
翻译准备中
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
This folder contains the LivSight delivery management system:
• A web dashboard (React) for agencies and super admins
• A backend REST API (Node/Express)
The WhatsApp bot lives in a separate repository.
If you’re new here, start with the Quickstart below, then use the deeper READMEs for each sub-app.
Key ideas:
• UI “Prestataire” = backend groups.
• Deliveries are created via REST API calls (dashboard / vendor routes).
• The API uses JWT in an HTTP-only cookie by default; mobile clients can use Bearer tokens when enabled (see API.md).查看完整 README ↗This folder contains the LivSight delivery management system:
The WhatsApp bot lives in a separate repository.
If you’re new here, start with the Quickstart below, then use the deeper READMEs for each sub-app.
flowchart LR
Api[server/src/api/server.js]
Db[(SQLite_or_Postgres)]
Web[client_(React_Dashboard)]
Web -->|HTTP_(cookies)| Api
Api -->|queries| Db
Key ideas:
groups.API.md).Top-level sub-apps:
client/: web dashboard (Vite + React + TypeScript + shadcn/ui + Tailwind)server/: REST API + DB layer (Node + Express)Reference docs (already in this folder):
REPO_DOCUMENTATION.md: full system overview and data modelAPI.md: HTTP API referenceProduction Deployment guide.md: deployment guidePRODUCTION_DEPLOYMENT_CHECKLIST.md: production checklistPRODUCTION_TROUBLESHOOTING.md: production troubleshootingDOMAIN_AND_DEPLOYMENT_SETUP.md: domain/DNS notesserver/)From saasDelivery/server/:
npm install
# Choose ONE:
# SQLite (simplest)
cp ENV_LOCAL_EXAMPLE.txt .env
# OR PostgreSQL
cp env.local.postgres.example .env
# Create tables
npm run migrate
# Run API (dev)
npm run dev
# Or explicitly:
npm run api:dev
Notes:
ALLOWED_ORIGINS (see server/src/api/server.js).server/.env (it contains secrets). Use the env.*.example files as templates.client/)From saasDelivery/client/:
npm install
cp .env.example .env.local
# Recommended: keep VITE_API_BASE_URL empty to use Vite proxy
# (see client/ENV_SETUP.md)
npm run dev
By default, the Vite dev server proxies /api/* to http://localhost:3000 (see client/vite.config.ts).
agency). Agencies own groups and deliveries.super_admin) who can manage multiple agencies.groups table.deliveries.vendor) used by /api/v1/vendor/* routes (mobile app use-case).stock_items.REPO_DOCUMENTATION.md for the end-to-end flow.client/README.md to learn the dashboard structure and conventions.server/README.md for backend scripts, env setup, migrations, and production notes.