LightRAG/scripts/DEV-STACK-README.md
Raphael MANSUY fe9b8ec02a
tests: stabilize integration tests + skip external services; fix multi-tenant API behavior and idempotency (#4)
* feat: Implement multi-tenant architecture with tenant and knowledge base models

- Added data models for tenants, knowledge bases, and related configurations.
- Introduced role and permission management for users in the multi-tenant system.
- Created a service layer for managing tenants and knowledge bases, including CRUD operations.
- Developed a tenant-aware instance manager for LightRAG with caching and isolation features.
- Added a migration script to transition existing workspace-based deployments to the new multi-tenant architecture.

* chore: ignore lightrag/api/webui/assets/ directory

* chore: stop tracking lightrag/api/webui/assets (ignore in .gitignore)

* feat: Initialize LightRAG Multi-Tenant Stack with PostgreSQL

- Added README.md for project overview, setup instructions, and architecture details.
- Created docker-compose.yml to define services: PostgreSQL, Redis, LightRAG API, and Web UI.
- Introduced env.example for environment variable configuration.
- Implemented init-postgres.sql for PostgreSQL schema initialization with multi-tenant support.
- Added reproduce_issue.py for testing default tenant access via API.

* feat: Enhance TenantSelector and update related components for improved multi-tenant support

* feat: Enhance testing capabilities and update documentation

- Updated Makefile to include new test commands for various modes (compatibility, isolation, multi-tenant, security, coverage, and dry-run).
- Modified API health check endpoint in Makefile to reflect new port configuration.
- Updated QUICK_START.md and README.md to reflect changes in service URLs and ports.
- Added environment variables for testing modes in env.example.
- Introduced run_all_tests.sh script to automate testing across different modes.
- Created conftest.py for pytest configuration, including database fixtures and mock services.
- Implemented database helper functions for streamlined database operations in tests.
- Added test collection hooks to skip tests based on the current MULTITENANT_MODE.

* feat: Implement multi-tenant support with demo mode enabled by default

- Added multi-tenant configuration to the environment and Docker setup.
- Created pre-configured demo tenants (acme-corp and techstart) for testing.
- Updated API endpoints to support tenant-specific data access.
- Enhanced Makefile commands for better service management and database operations.
- Introduced user-tenant membership system with role-based access control.
- Added comprehensive documentation for multi-tenant setup and usage.
- Fixed issues with document visibility in multi-tenant environments.
- Implemented necessary database migrations for user memberships and legacy support.

* feat(audit): Add final audit report for multi-tenant implementation

- Documented overall assessment, architecture overview, test results, security findings, and recommendations.
- Included detailed findings on critical security issues and architectural concerns.

fix(security): Implement security fixes based on audit findings

- Removed global RAG fallback and enforced strict tenant context.
- Configured super-admin access and required user authentication for tenant access.
- Cleared localStorage on logout and improved error handling in WebUI.

chore(logs): Create task logs for audit and security fixes implementation

- Documented actions, decisions, and next steps for both audit and security fixes.
- Summarized test results and remaining recommendations.

chore(scripts): Enhance development stack management scripts

- Added scripts for cleaning, starting, and stopping the development stack.
- Improved output messages and ensured graceful shutdown of services.

feat(starter): Initialize PostgreSQL with AGE extension support

- Created initialization scripts for PostgreSQL extensions including uuid-ossp, vector, and AGE.
- Ensured successful installation and verification of extensions.

* feat: Implement auto-select for first tenant and KB on initial load in WebUI

- Removed WEBUI_INITIAL_STATE_FIX.md as the issue is resolved.
- Added useTenantInitialization hook to automatically select the first available tenant and KB on app load.
- Integrated the new hook into the Root component of the WebUI.
- Updated RetrievalTesting component to ensure a KB is selected before allowing user interaction.
- Created end-to-end tests for multi-tenant isolation and real service interactions.
- Added scripts for starting, stopping, and cleaning the development stack.
- Enhanced API and tenant routes to support tenant-specific pipeline status initialization.
- Updated constants for backend URL to reflect the correct port.
- Improved error handling and logging in various components.

* feat: Add multi-tenant support with enhanced E2E testing scripts and client functionality

* update client

* Add integration and unit tests for multi-tenant API, models, security, and storage

- Implement integration tests for tenant and knowledge base management endpoints in `test_tenant_api_routes.py`.
- Create unit tests for tenant isolation, model validation, and role permissions in `test_tenant_models.py`.
- Add security tests to enforce role-based permissions and context validation in `test_tenant_security.py`.
- Develop tests for tenant-aware storage operations and context isolation in `test_tenant_storage_phase3.py`.

* feat(e2e): Implement OpenAI model support and database reset functionality

* Add comprehensive test suite for gpt-5-nano compatibility

- Introduced tests for parameter normalization, embeddings, and entity extraction.
- Implemented direct API testing for gpt-5-nano.
- Validated .env configuration loading and OpenAI API connectivity.
- Analyzed reasoning token overhead with various token limits.
- Documented test procedures and expected outcomes in README files.
- Ensured all tests pass for production readiness.

* kg(postgres_impl): ensure AGE extension is loaded in session and configure graph initialization

* dev: add hybrid dev helper scripts, Makefile, docker-compose.dev-db and local development docs

* feat(dev): add dev helper scripts and local development documentation for hybrid setup

* feat(multi-tenant): add detailed specifications and logs for multi-tenant improvements, including UX, backend handling, and ingestion pipeline

* feat(migration): add generated tenant/kb columns, indexes, triggers; drop unused tables; update schema and docs

* test(backward-compat): adapt tests to new StorageNameSpace/TenantService APIs (use concrete dummy storages)

* chore: multi-tenant and UX updates — docs, webui, storage, tenant service adjustments

* tests: stabilize integration tests + skip external services; fix multi-tenant API behavior and idempotency

- gpt5_nano_compatibility: add pytest-asyncio markers, skip when OPENAI key missing, prevent module-level asyncio.run collection, add conftest
- Ollama tests: add server availability check and skip markers; avoid pytest collection warnings by renaming helper classes
- Graph storage tests: rename interactive test functions to avoid pytest collection
- Document & Tenant routes: support external_ids for idempotency; ensure HTTPExceptions are re-raised
- LightRAG core: support external_ids in apipeline_enqueue_documents and idempotent logic
- Tests updated to match API changes (tenant routes & document routes)
- Add logs and scripts for inspection and audit
2025-12-04 16:04:21 +08:00

255 lines
5 KiB
Markdown

# LightRAG Development Stack Scripts
Quick start, stop, and clean scripts for the LightRAG multi-tenant development environment.
## Quick Start
```bash
# Start all services
bash scripts/start-dev-stack.sh
# Stop all services (data persists)
bash scripts/stop-dev-stack.sh
# Complete cleanup (removes all data)
bash scripts/clean-dev-stack.sh
```
## Scripts Overview
### 🚀 `start-dev-stack.sh`
Starts the complete development stack with all services.
**What it does:**
1. Starts Docker containers (PostgreSQL + Redis)
2. Waits for PostgreSQL to be ready
3. Starts LightRAG API Server on port 9621
4. Starts React WebUI dev server on port 5173
**Usage:**
```bash
bash scripts/start-dev-stack.sh
```
**Output:**
```
✅ Stack Started Successfully!
Services Running:
• PostgreSQL: localhost:5433 (lightrag_audit)
• Redis: localhost:6380
• API: http://localhost:9621
• WebUI: http://localhost:5173
Useful Links:
• API Docs: http://localhost:9621/docs
• OpenAPI: http://localhost:9621/openapi.json
```
**Features:**
- Automatic PostgreSQL health check
- Automatic API health check
- Automatic WebUI readiness check
- Saves process IDs for later cleanup
- Creates log files in `/tmp/lightrag-*.log`
---
### 🛑 `stop-dev-stack.sh`
Gracefully stops all services while preserving data.
**What it does:**
1. Stops API Server
2. Stops WebUI Server
3. Stops Docker containers
4. Preserves all data in Docker volumes
**Usage:**
```bash
bash scripts/stop-dev-stack.sh
```
**Note:** All data is preserved in Docker volumes. To completely reset, use `clean-dev-stack.sh`.
---
### 🧹 `clean-dev-stack.sh`
Completely removes all containers, volumes, and data. **WARNING: Destructive operation!**
**What it does:**
1. Confirms action (requires "yes" response)
2. Kills all background processes
3. Stops Docker containers
4. Removes Docker volumes
5. Clears log files
6. Cleans local storage (rag_storage directory)
**Usage:**
```bash
bash scripts/clean-dev-stack.sh
```
**Warning:**
- 🚨 ALL DATABASE DATA WILL BE DELETED
- 🚨 ALL LOCAL RAG STORAGE WILL BE DELETED
- 🚨 Requires confirmation before proceeding
---
## Service Endpoints
Once started, the following services are available:
### API Server
- **Base URL:** `http://localhost:9621`
- **API Documentation:** `http://localhost:9621/docs`
- **OpenAPI Schema:** `http://localhost:9621/openapi.json`
- **Health Check:** `http://localhost:9621/health`
- **Login:** `POST http://localhost:9621/login`
### WebUI
- **URL:** `http://localhost:5173`
- **Framework:** React + Vite
### Databases
- **PostgreSQL:** `localhost:5433` (default database: `lightrag_audit`)
- User: `lightrag`
- Password: `lightrag123`
- **Redis:** `localhost:6380`
### Authentication
- **Default Admin User:** `admin`
- **Default Admin Password:** `admin123`
---
## Configuration
The scripts use these environment variables (all set automatically):
```bash
POSTGRES_HOST=localhost
POSTGRES_PORT=5433
POSTGRES_USER=lightrag
POSTGRES_PASSWORD=lightrag123
POSTGRES_DATABASE=lightrag_audit
REDIS_HOST=localhost
REDIS_PORT=6380
LIGHTRAG_MULTI_TENANT_STRICT=true
LIGHTRAG_REQUIRE_USER_AUTH=true
AUTH_USER=admin
AUTH_PASS=admin123
LLM_BINDING=ollama
LLM_BINDING_HOST=http://localhost:11434
EMBEDDING_BINDING=ollama
EMBEDDING_BINDING_HOST=http://localhost:11434
```
---
## Viewing Logs
After starting the stack, view logs with:
```bash
# API Server logs
tail -f /tmp/lightrag-api.log
# WebUI logs
tail -f /tmp/lightrag-webui.log
# Docker PostgreSQL logs
docker logs lightrag-audit-postgres
# Docker Redis logs
docker logs lightrag-audit-redis
```
---
## Troubleshooting
### API Server won't start
```bash
# Check if port 9621 is already in use
lsof -i :9621
# View full API logs
cat /tmp/lightrag-api.log
# Kill any orphaned processes
pkill -9 -f lightrag.api.lightrag_server
```
### PostgreSQL connection error
```bash
# Check PostgreSQL is running
docker ps | grep lightrag-audit-postgres
# Check PostgreSQL logs
docker logs lightrag-audit-postgres
# Restart PostgreSQL container
docker restart lightrag-audit-postgres
```
### WebUI not loading
```bash
# Check if port 5173 is already in use
lsof -i :5173
# View WebUI logs
cat /tmp/lightrag-webui.log
# Ensure Node.js dependencies are installed
cd lightrag_webui && npm install
```
### Docker volume cleanup issues
```bash
# List all volumes
docker volume ls
# Remove specific volume manually
docker volume rm lightrag_postgres_audit_data
# Remove all unused volumes
docker volume prune
```
---
## Process Management
The scripts save process IDs for clean shutdown:
- **API Server PID:** `/tmp/lightrag-api.pid`
- **WebUI PID:** `/tmp/lightrag-webui.pid`
These are automatically used by the stop script for graceful shutdown.
---
## Monitoring
Check running processes:
```bash
# List all LightRAG processes
ps aux | grep -E "lightrag|npm run dev" | grep -v grep
# Check specific ports
netstat -an | grep -E "9621|5173|5433|6380"
```
---
## Requirements
- Docker and Docker Compose
- Python 3.10+
- Node.js 18+
- npm or yarn
- macOS/Linux (for bash scripts)