- Switch from package.json to package.runtime.json in runtime stage
- Reduces image size by 82% (from ~1.5GB to ~280MB)
- 10x faster builds (1-2 minutes vs 12 minutes)
- No functional changes - uses pre-built database from git
- Aligns Railway image with main Dockerfile optimization
This dramatically improves Railway deployment performance while
maintaining full functionality.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add Railway-specific Docker image build to CI/CD workflow
- Builds n8n-mcp-railway image alongside standard image
- Railway image optimized for AMD64 architecture
- Automatically published to ghcr.io on main branch pushes
- Create comprehensive Railway deployment documentation
- Step-by-step deployment guide with security best practices
- Claude Desktop connection instructions via mcp-remote
- Troubleshooting guide for common issues
- Architecture details and single-instance design explanation
- Update README with Railway documentation link
- Removed inline Railway content to keep README focused
- Added link to dedicated Railway deployment guide
This enables zero-configuration cloud deployment of n8n-mcp
with automatic HTTPS, global access, and built-in monitoring.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Rolled back README.md to remove Railway deployment instructions while keeping the codebase changes intact. This addresses any confusion about deployment methods without breaking existing Railway deployments.
- Add Railway as Option 4 in Quick Start section per review request
- Include brief explanation of Railway platform
- Add deploy button with proper placement
- Document setup instructions and environment variables
- Add AUTH_TOKEN configuration note
- Include database availability requirements note
- Configure Claude Desktop integration via mcp-remote
This commit implements the documentation requirements from PR #53 review,
completing the Railway deployment feature.
- Fixed docker-entrypoint.sh to use NODE_DB_PATH instead of hardcoded paths
- Added log_message() helper to prevent stdio mode output corruption
- Fixed directory creation race condition with proper ownership
- Added path validation to ensure NODE_DB_PATH ends with .db
- Updated rebuild.ts to respect NODE_DB_PATH environment variable
- Added comprehensive documentation for custom database paths
- Bumped version to 2.7.16
The bug was caused by hardcoded /app/data/nodes.db paths in the Docker
entrypoint script that ignored the NODE_DB_PATH environment variable.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create dedicated setup documentation for each IDE
- Add Claude Code setup with proper CLI commands and screenshots
- Add Cursor setup with video tutorial and MCP configuration
- Add Windsurf setup with video tutorial and settings instructions
- Update README to consolidate IDE setup under "Connect your IDE" section
- Include visual guides with screenshots for better user experience
- Link all IDE guides to main Claude Project Setup instructions
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
