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。 以下为已保存的摘录。
Ayurvedic inventory & manufacturing ERP for Atharva Nature Healthcare —
proposed rebuild of invento-nextgen, designed against
Invento-Modular-Requirements.docx (v2) and reviewed screen by screen.
Start here: docs/DESIGN.md — full architecture,
database schema, and per-module design. Then docs/modules/
— one short doc per screen, meant to be reviewed the same way the Word
document was, module by module.
Next.js 16 (App Router, TypeScript) · Supabase (Postgres + Auth, Row Level
Security) · Tailwind CSS v4 · Recharts · jsPDF.查看完整 README ↗Ayurvedic inventory & manufacturing ERP for Atharva Nature Healthcare —
proposed rebuild of invento-nextgen, designed against
Invento-Modular-Requirements.docx (v2) and reviewed screen by screen.
Start here: docs/DESIGN.md — full architecture,
database schema, and per-module design. Then docs/modules/
— one short doc per screen, meant to be reviewed the same way the Word
document was, module by module.
Next.js 16 (App Router, TypeScript) · Supabase (Postgres + Auth, Row Level Security) · Tailwind CSS v4 · Recharts · jsPDF.
Full walkthrough: supabase/README.md (building the
database from fresh-install.sql, the dashboard settings that live outside
SQL, the Vercel variables) and docs/SUPABASE_SETUP.md
(project creation, Auth configuration, first admin, deploying). Short version:
supabase/fresh-install.sql in the SQL
Editor (a brand-new, empty project only). An existing database only needs
the newest files in supabase/migrations/ that it has not run yet..env.example to .env.local and fill in your project's URL, anon
key and service role key (Project Settings → API).npm installnpm run dev — http://localhost:3000system_admin (the User Roles screen is itself admin-only,
so the first admin has to be bootstrapped outside the app — see the
comment at the top of scripts/seed-admin.ts):
SUPABASE_SERVICE_ROLE_KEY=... NEXT_PUBLIC_SUPABASE_URL=... \
npx tsx scripts/seed-admin.ts [email protected]
All 15 modules from the requirements document, plus auth/roles/profile:
| Module | Route |
|---|---|
| Login & Registration | /login, /register, /forgot-password, /reset-password |
| Item Type Master | /item-types |
| Item Master | /items |
| Vendor Master | /vendors |
| Purchase | /purchase |
| Quality Control | /qc |
| Inventory Ledger | /inventory, /inventory/balance, /inventory/rm-report |
| MFR | /mfr |
| Finished Product | /finished-product |
| Batch Manufacturing Record | /bmr |
| Packaging | /packaging |
| Label Printing | /labels |
| Certificate of Analysis | /coa |
| Line Clearance | /line-clearance |
| Environmental Control | /environmental-control |
| SOP / STP Documents | /documents |
| User Roles & Access | /user-roles |
| Dashboard | / |
| Reports | /reports |
Proposed design + a full working implementation of every module, built for
review — not yet signed off by Ravi/Atharva module by module. Known
simplifications and open items are listed in docs/DESIGN.md §9, and each
docs/modules/*.md doc calls out anything that agent deviated from the
spec while building, with why. Nothing here has been run against a live
Supabase project yet — do the local setup above and page through it before
treating any module as final.