Local Development Workflow
Initial Setup
Create project
helix init with no arguments defaults to making a local instance called dev.Development Iteration
When making changes during development:Working with Multiple Instances
Create different instances for different purposes:Multi-Environment Setup
Development → Staging → Production
- Setup
- Deploy
- Rollback
Cloud Deployment Workflows
Helix Cloud Deployment
Fly.io Deployment
Prerequisites: Install and authenticateflyctl
AWS ECR Deployment
Prerequisites: Configure AWS CLIPush to ECR
- Create ECR repository if needed
- Authenticate Docker with ECR
- Tag and push the image
Best Practices
Development Best Practices
Development Best Practices
- Always run
helix checkbefore deploying - Use descriptive instance names
- Keep development and production configurations separate
- Regularly clean up unused resources with
helix prune - Version control your
helix.tomlfile
Production Best Practices
Production Best Practices
- Use
build_mode = "release"for production - Configure appropriate vector parameters for your data scale
- Enable monitoring and logging
- Set up automated backups
- Test migrations in staging first
Security Best Practices
Security Best Practices
- Never commit credentials to version control
- Use environment variables for sensitive data
- Regularly rotate API keys
- Keep CLI updated with
helix update - Use private instances for production data