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.
Translation pending
A unified operations platform that manages customers, catalogue, attendance, finance, and team across every branch.
AI translation
Unified operations platform: customers, catalogue, attendance, finance and team across every branch.
BusinessTypeScript · HTMLGitHub @caratsenseOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
This is the clean, self-contained working copy of the Eclat project, kept on the internal C: drive so it does not depend on the large E:\ archive.
What's here (everything needed to build & run)
• frontend/ — Next.js 16 app (run: cd frontend && npm run dev → http://localhost:3000)
• backend/ — NestJS API + Prisma (run: cd backend && npm run start:dev → http://localhost:4000)
• docs/ — all project docs. Start with docs/HANDOFF.md.
• data_sync/— the on-site SJEP→Eclat sync agent (EclatSync/sync_sjep.py)
• .claude/ — agent definitions
• CLAUDE.md — agent context (read first)Read the full README ↗This is the clean, self-contained working copy of the Eclat project, kept on the internal C: drive so it does not depend on the large E:\ archive.
frontend/ — Next.js 16 app (run: cd frontend && npm run dev → http://localhost:3000)backend/ — NestJS API + Prisma (run: cd backend && npm run start:dev → http://localhost:4000)docs/ — all project docs. Start with docs/HANDOFF.md.synceclatcaratsense/ — the on-site Gati (SJEP) → Eclat sync agent (sync_sjep.py, sync_media.py). How it is installed and run on APPSERVER: GATI_DB_SYNC.md. (data_sync/EclatSync and HANDOVER/EclatSync are obsolete.).claude/ — agent definitionsCLAUDE.md — agent context (read first)The app uses PostgreSQL eclat_dev on this machine's local Postgres (not stored in this folder). It already holds the seeded demo data plus the real legacy backfill (564 parties, 753 products, 2,690 stock pieces, 239 sales…). Connection is in backend/.env (DATABASE_URL).
The legacy reference archive stays on E:\Eclat Project\:
SJEP BACKUP/ (~525 GB of dated .bak files) — reference onlySJEP DATA/ (live .mdf), SJEP REPORT/ (DevExpress .repx + requirements PDF)Why it's safe to leave them behind: everything we needed from the backups was already extracted — the schema is mapped (docs/legacy-schema.md) and the real data was backfilled into Postgres. In production the app syncs from the client's live SQL Server, not these backups. Keep the E:\ archive only for re-restore / audit if ever needed.
@caratsense, @adi-caratsense (GitHub)cd backend && npm install then cd ../frontend && npm installbackend/.env DATABASE_URL; cd backend && npx prisma migrate deploy && node prisma/seed.mjsnpm run start:dev) and frontend (npm run dev). Log in at /login (see backend/README.md for demo accounts).