graphiti/railway.json
Tyler Lafleur 6a11643a94 Comprehensive Railway deployment fix: eliminate cache mount errors
MAJOR CHANGES:
- Replace complex uv-based Dockerfile with simple pip-only approach
- Add requirements.txt for standard Python dependency management
- Remove all uv commands that might trigger cache mount behavior
- Add .dockerignore for clean Railway build context
- Add nixpacks.toml to force Dockerfile usage (disable auto-detection)
- Update railway.json with explicit Docker configuration

PROBLEM SOLVED:
Railway 'Cache mount ID is not prefixed with cache key' error should be resolved
by eliminating all potential sources of cache mount directives.

DEPLOYMENT STRATEGY:
- Single-stage Docker build using standard pip
- Install graphiti-core from source with 'pip install .'
- Install MCP dependencies with 'pip install -r requirements.txt'
- No complex build tools or caching mechanisms
- Explicit Railway Docker configuration

🚀 Generated with Claude Code (https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-19 19:58:40 -05:00

13 lines
No EOL
275 B
JSON

{
"$schema": "https://railway.app/railway.schema.json",
"build": {
"builder": "dockerfile",
"dockerfilePath": "Dockerfile",
"buildArgs": {}
},
"deploy": {
"numReplicas": 1,
"restartPolicyType": "on_failure",
"restartPolicyMaxRetries": 10
}
}