Deployment
This section covers production deployment of PATH DRC EMR.
Deployment Decision Tree
Choose your deployment approach based on your environment:
graph TD
Start{What's your environment?} -->|Internet available| Online[Online Installation]
Start -->|No internet/Air-gapped| Offline[Offline Installation]
Online --> Site{Need site-specific config?}
Offline --> Site
Site -->|Yes - Akram/Libikisi| SiteSpecific[Site-Specific Build]
Site -->|No - Standard| Base[Base Distribution]
style Online fill:#e8f5e9
style Offline fill:#fff3e0
style SiteSpecific fill:#e1f5fe
style Base fill:#f3e5f5
Deployment Approaches
Online Installation
Best for environments with reliable internet connectivity. Images are pulled directly from GitHub Container Registry.
Pros: Simple setup, automatic access to latest updates, smaller initial download
Cons: Requires internet during installation, requires GitHub authentication
Offline Installation
Best for air-gapped environments or locations with limited internet. Uses pre-packaged image bundles.
Pros: No internet required after bundle download, predictable installation
Cons: Larger initial file transfer, manual update process
Site-Specific Builds
Use pre-configured builds for specific facilities (Akram, Libikisi) with customized metadata.
What’s in This Section
- Online Installation: Step-by-step guide for internet-connected deployments
- Offline Installation: Air-gapped installation procedures
- Site-Specific Builds: Using facility-specific configurations
- Environment Variables: Complete
.envreference
Comparison Table
| Feature | Online | Offline | Site-Specific |
|---|---|---|---|
| Internet Required | During install | No | During install* |
| Setup Complexity | Low | Medium | Low-Medium |
| Customization | Full | Full | Pre-configured |
| Update Process | Simple | Manual | Simple |
*Offline bundles also available for site-specific builds