Production Deployment
Production OpenFactory deployments should be treated as a core software platform. Plan capacity, security, monitoring, backup, upgrade, and incident response before opening access to users.
Production Checklist
| Area | Checklist |
|---|---|
| TLS and DNS | Stable domains, managed certificates, and documented renewal |
| Identity | SSO configured, admin access tested, break-glass process documented |
| Secrets | Secrets stored outside source control with rotation procedures |
| Storage | Durable artifact storage with backups and retention policy |
| Compute | Build and VM capacity sized for expected concurrency |
| Monitoring | Health checks, logs, alerts, and audit exports configured |
| Security | Firewall rules, least-privilege roles, and access reviews in place |
| Updates | Signed release process and rollback plan documented |
Backups
Back up:
- Organization configuration
- Build recipes and metadata
- Artifact indexes and retained artifacts
- Audit logs and compliance evidence
- Integration configuration
Test restore procedures before relying on the deployment for production work.
Air-Gapped Environments
Air-gapped deployments require additional planning:
- Approved package mirrors or mirrored repositories
- Offline release package transfer
- Artifact export process
- Offline license and update procedure
- Local identity and logging dependencies
OpenFactory support will provide an environment-specific runbook for approved air-gapped deployments.
Last updated on