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
Warehouse vehicle pre-shift inspection
Translation pending
BusinessTypeScript · CSSGitHub @PI-Team-ProjectOnlineOwner 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
Holland 담당자 Bum Yoon Kim
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗This is a Next.js project bootstrapped with create-next-app.
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
Note: npm run dev runs against the local staging database, not production. npm run dev:prod exists for the rare case where you genuinely need production data in front of you — it shares the real DATABASE_URL from .env, so anything that writes data or touches the schema hits live records. There is no separate cloud staging environment; the local one below is it.
npm test # run once
npm run test:watch
Covers the core scoring logic (src/lib/review.ts), shift/date math (src/lib/shifts.ts), and the fleet-status logic in src/app/dashboard/inspectionRow.ts — including a regression test for a real bug where a vehicle's status came from only its most recent inspection, letting an unconfirmed safety flag get silently cleared by a later "all good" shift.
A real, persistent Postgres database (via prisma dev) that is not the shared dev/production database — use it for anything risky: schema changes, data migrations, or testing under realistic data volume.
npm run db:staging # start it (safe to re-run; a no-op if already running)
npm run db:staging:migrate # apply the current schema
npm run db:staging:seed # fill it with ~a month of realistic synthetic inspections
npm run dev:staging # run the app against it instead of the real database
Connection details live in .env.staging (gitignored, machine-specific). If the named server is ever removed and recreated, its port may change — run npx prisma dev ls and update the DATABASE_URL in .env.staging to match.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
To learn more about Next.js, take a look at the following resources:
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.