Skip to content
Docs
Contact Us

Best Practices

Best Practices

Section titled “Best Practices”

Follow these best practices when using MirthSync in production environments.

Security

Section titled “Security”
  • Never commit credentials to Git
  • Use environment variables for sensitive data
  • Implement least-privilege access
  • Rotate credentials regularly
  • Use HTTPS for Mirth Connect API access

Version Control

Section titled “Version Control”
  • Write descriptive commit messages
  • Use feature branches for development
  • Require pull request reviews
  • Tag releases with semantic versioning
  • Keep commits atomic and focused

Deployment

Section titled “Deployment”
  • Test in staging before production
  • Use CI/CD for automated deployments
  • Implement rollback procedures
  • Monitor deployments
  • Document deployment processes

Collaboration

Section titled “Collaboration”
  • Document channel purposes and configurations
  • Use clear naming conventions
  • Review changes before merging
  • Maintain a CHANGELOG
  • Communicate breaking changes

Next Steps

Section titled “Next Steps”