gmakstutis/graphiti
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
685 commits 43 branches 175 tags 21 MiB
Commit graph

6 commits

Author SHA1 Message Date
Daniel Chalef
057056270a docs: Consolidate Docker READMEs into single comprehensive guide 
- Merge README-kuzu.md content into main Docker README.md
- Add complete FalkorDB documentation with configuration and gotchas
- Remove editorializing about which database is 'best' or 'recommended'
- Provide equal treatment for all three databases (KuzuDB, Neo4j, FalkorDB)
- Include specific gotchas and troubleshooting for each database
- Add detailed backup/restore procedures for each database type
- Document all environment variables and configuration options
- Remove pros/cons sections and performance comparison editorializing
- Delete redundant README-kuzu.md file

The documentation now provides factual, unbiased instructions for using
any of the three supported graph databases.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-08-30 09:04:34 -07:00
Daniel Chalef
f1536faff8 refactor: Reorganize Docker Compose files by database type 
- Rename docker-compose.yml to docker-compose-neo4j.yml for Neo4j setup
- Rename docker-compose-kuzu.yml to docker-compose.yml (making KuzuDB default)
- Create docker-compose-falkordb.yml for FalkorDB deployment
- Add dedicated config files for each database type:
  - config-docker-neo4j.yaml for Neo4j
  - config-docker-falkordb.yaml for FalkorDB
  - config-docker-kuzu.yaml for KuzuDB
- Create comprehensive Docker README with database comparison
- Update all compose files to use their respective config files

KuzuDB is now the default database for Docker deployments due to:
- No external dependencies required
- Lower resource usage
- Instant startup time
- Simpler deployment

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-08-30 08:50:48 -07:00
Daniel Chalef
fb2ebeba50 feat: Configure KuzuDB Docker deployment with persistent storage 
- Update docker-compose-kuzu.yml to use persistent volume by default
- Set KUZU_DB to /data/graphiti.kuzu for persistent storage
- Increase max concurrent queries from 1 to 10 for better performance
- Add dedicated config-docker-kuzu.yaml for Docker deployments
- Create README-kuzu.md with usage instructions and troubleshooting
- Configure volume with local driver for data persistence

The setup now provides:
- Automatic data persistence across container restarts
- No external database dependencies
- Simple backup/restore procedures
- Lower resource usage compared to Neo4j

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-08-30 08:50:48 -07:00
Daniel Chalef
2e345698e4 feat: Add KuzuDB support to MCP server and make it default 
- Add KuzuProviderConfig to schema for KuzuDB configuration
- Update DatabaseDriverFactory to support KuzuDB initialization
- Modify GraphitiService to handle KuzuDB driver instantiation
- Update CLI argument parser to include 'kuzu' option
- Make KuzuDB the default database provider (in-memory by default)
- Add docker-compose-kuzu.yml for standalone KuzuDB deployment
- Fix FalkorDB factory to parse URI into host/port parameters
- Fix EntityNode type access (use labels[0] instead of type)
- Add kuzu dependency to MCP server pyproject.toml

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-08-30 08:50:48 -07:00
Daniel Chalef
694ea46f66 fix: Resolve CI/CD issues for MCP server 
- Fixed code formatting with ruff (removed trailing whitespace)
- Fixed linting issues (removed unused imports)
- Updated Dockerfile for new directory structure
- Improved FalkorDB container health checks and timeouts
- Enhanced FalkorDB readiness check with GRAPH module verification
- Added debugging for FalkorDB startup failures

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-08-30 08:50:48 -07:00
Daniel Chalef
3c25268afc feat: Major MCP server refactor with improved structure and CI/CD 
- Reorganized MCP server into clean, scalable directory structure:
  - `src/config/` - Configuration modules (schema, managers, provider configs)
  - `src/services/` - Services (queue, factories)
  - `src/models/` - Data models (entities, responses)
  - `src/utils/` - Utilities (formatting, helpers)
  - `tests/` - All test files
  - `config/` - Configuration files (YAML, examples)
  - `docker/` - Docker setup files
  - `docs/` - Documentation

- Added `main.py` wrapper for seamless transition
- Maintains existing command-line interface
- All deployment scripts continue to work unchanged

- **Queue Service Interface Fix**: Fixed missing `add_episode()` and `initialize()` methods
  - Server calls at `graphiti_mcp_server.py:276` and `:755` now work correctly
  - Eliminates runtime crashes on startup and episode processing
- Updated imports throughout restructured codebase
- Fixed Python module name conflicts (renamed `types/` to `models/`)

- **MCP Server Tests Action** (`.github/workflows/mcp-server-tests.yml`)
  - Runs on PRs targeting main with `mcp_server/**` changes
  - Configuration validation, syntax checking, unit tests
  - Import structure validation, dependency verification
  - Main.py wrapper functionality testing

- **MCP Server Lint Action** (`.github/workflows/mcp-server-lint.yml`)
  - Code formatting with ruff (100 char line length, single quotes)
  - Comprehensive linting with GitHub-formatted output
  - Type checking with pyright (baseline approach for existing errors)
  - Import sorting validation

- Added ruff and pyright configuration to `mcp_server/pyproject.toml`
- Proper tool configuration for the new structure
- Enhanced development dependencies with formatting/linting tools

- All existing tests moved and updated for new structure
- Import paths updated throughout test suite
- Validation scripts enhanced for restructured codebase

- **Improved Maintainability**: Clear separation of concerns
- **Better Scalability**: Organized structure supports growth
- **Enhanced Developer Experience**: Proper linting, formatting, type checking
- **Automated Quality Gates**: CI/CD ensures code quality on every PR
- **Zero Breaking Changes**: Maintains full backwards compatibility

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-08-30 08:50:48 -07:00