- 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>
- Add paths-ignore to skip Docker builds for documentation-only changes
- Remove problematic branch prefix from SHA tags to fix invalid tag format
- This prevents unnecessary builds for changes to .md files, FUNDING.yml, etc.
- Added no-cache: true to docker/build-push-action
- Previous builds were aggressively caching the old database from 13:18
- This forces a complete rebuild including the new database with trigger fixes
- Build will take longer (5-10min vs 26sec) but ensures correct database
The cache was so aggressive that even Dockerfile changes didn't invalidate it.
This nuclear option ensures the trigger detection fixes for webhook, cron,
interval, and emailReadImap nodes are finally included in the Docker image.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added 'lfs: true' to all checkout steps in workflows
- Ensures Docker builds get the actual database file, not LFS pointer
- Required after migrating nodes.db to Git LFS
Major optimization that reduces Docker image size by 87% and build time by 10x:
- Remove ALL n8n dependencies from runtime Docker image
- Add package.runtime.json with only 5 essential runtime deps
- Optimize Dockerfile to build TypeScript without n8n packages
- Add BuildKit optimizations with cache mounts
- Update documentation to highlight the improvements
Results:
- Image size: ~1.5GB → ~200MB (87% reduction)
- Build time: ~12 minutes → ~1-2 minutes
- No n8n version conflicts at runtime
- Better security with minimal attack surface
The key insight is that since we always rebuild the database locally
before deployment, the Docker runtime never needs n8n packages.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
## Root cause
- Docker buildx memory options were incorrectly formatted
- Database build during Docker image creation was failing on multi-platform builds
- n8n native dependencies caused issues across different architectures
## Solution
- Removed invalid buildx driver-opts configuration
- Eliminated database build stage from Dockerfile
- Now using pre-built nodes.db file (11MB) from repository
- Fixed .dockerignore to include nodes.db in build context
- Added .dockerignore to version control (was incorrectly gitignored)
## Benefits
- Faster builds (no n8n package installation during build)
- More reliable multi-platform builds (amd64 + arm64)
- Simpler Dockerfile (3 stages instead of 4)
Database can still be rebuilt locally using 'npm run rebuild' when needed.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Rename Dockerfile.optimized to Dockerfile (now the default)
- Keep old Dockerfile as Dockerfile.old for reference
- Update GitHub Actions to use default Dockerfile
- Remove build-full job - only one image variant now
- Remove docker-compose.optimized.yml and other variants
- Update all documentation to reflect single image approach
The optimized 283MB image is now the only n8n-MCP Docker image.
This simplifies the user experience and provides the best solution
for all use cases.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Change main build to use Dockerfile.optimized (targets ~200MB image)
- Add separate 'full' build job for development variant (2.6GB)
- Update tagging strategy: 'latest' for optimized, 'full' suffix for full variant
- Update documentation to reflect dual image strategy
- Update docker-compose.yml with variant selection comment
This provides users with two options:
- Optimized (default): Pre-built database, minimal size, for production
- Full: Complete n8n packages, dynamic scanning, for development
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
