3e09802db8
- Non-prod workflow: builds on push to main, pushes to acme-nonprod registry, creates Octopus release in Non-Prod channel - Prod workflow: builds on v* tags, pushes to acme-prod registry, creates Octopus release in Prod channel - Simple Alpine Dockerfile for demo purposes
632 B
632 B
Demo App — Dual Image Channel Pattern
Demonstrates Octopus Deploy's channel pattern for routing non-prod and prod container images through separate lifecycles.
How it works
- Push to
main→ builds non-prod image → pushes toacme-nonprod/demo-app→ creates Octopus release in Non-Prod channel - Push a
v*tag → builds prod image → pushes toacme-prod/demo-app→ creates Octopus release in Prod channel
Each channel has its own lifecycle:
- Non-Prod: Development → Staging (cannot reach Production)
- Prod: Staging → Production