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
The Protocol Labs Directory drives breakthroughs in computing to push humanity forward.
Translation pending
BusinessTypeScript · SCSSGitHub @memser-spaceportOnlineOwner 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 frontend for the Directory application, uses Next.js framework and is bootstrapped with create-next-app.
Link to the index repo
This project is using Next.js version 14.2.3.
To learn more about Next.js, take a look at the following resources:
• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository
The folder structure of this project is organized as follows:Read the full README ↗This is the frontend for the Directory application, uses Next.js framework and is bootstrapped with create-next-app.
Link to the index repo
This project is using Next.js version 14.2.3.
To learn more about Next.js, take a look at the following resources:
You can check out the Next.js GitHub repository
The folder structure of this project is organized as follows:
app/: Contains the main application files, including pages and layout components.
components/: Contains reusable components categorized into:
services/: Contains service files that handle API calls and business logic.
utils/: Utility functions that can be used throughout the application.
analytics/: Contains files related to analytics tracking and reporting.
public/: Contains static assets such as images, fonts, and other resources.
__tests__/: Contains test files for the application. And its maintains the same folder structure as components.
| Name | Type | Purpose | Mandatory |
|---|---|---|---|
| Privy | External | The hybrid auth solution provider for users to login | Yes |
| PostHog | External | For analytics purpose | No |
| Directory Backend | Internal | For communicating to the directory database through REST API | Yes |
| Husky (sandbox mode) | Internal | To leverage the AI assist feature | No |
| PL Auth service (sandbox mode) | Internal | To manage user auth requests and issue tokens, works in OAuth 2.0 standard | Yes |
To install the dependencies use the below command
npm install
Use the below command to create .env using .env.example
cp .env.example .env
Set the env variables based on the instructions provided in the .env.example file.
For local development use the test values mentioned in the comments for each env variable.
Open the terminal and run the following command:
npm run dev
Application will be running on http://localhost:4200
To run the tests, use the following command:
npm run test
Follow the instructions here to setup and run the directory admin frontend.