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
Tableau de bord moderne pour agence de livraison. Gérez vos livraisons, paiements et expéditions.
Translation pending
BusinessTypeScript · JavaScriptGitHub @Ericdt17OnlineOwner 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 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).Read the full 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.