📘Container Deployment Guide
9 min
Overview
This guide explains how to deploy Docuflow using sample YAML files or integrating with your CI/CD pipeline.
📦 Provided YAML Configurations
We offer example YAML files for:
- Deployment
- Service
- Route
These can be used as templates or modified to suit your environment.
🐳 Container Registry & Tags
Docuflow containers are published to our Container Registry: versafile.azurecr.io
Pull credential for the container registry will be provides by your account manager
Available image tags:
- latesttags the latest image of that version
- qa-latesttags the qa-latest image of that version, will be typically released 1 week before tagged as latest
- date-stamp (e.g., 20250710) the tag will stay and is available for up to 12month.
Example: versafile.azurecr.io/docuflow/6.9/df4sap:latest
You may:
- Pull directly from our Container Registry
- Copy to your own container registry
🌐 Ingress Configuration
Supported ingress methods:
- Ingress or Route
- Service Type: LoadBalancer
Ingress or Route: Currently each port should have a dedicated ingress/route configuration:
- 1 for Docuflow GUI
- 1 per ArchiveLink or CMIS content server
- 1 per WebSocket RFC Connection
Service Type: LoadBalancer
- One per Docuflow deployment
🗂️ Storage and Configuration
Docuflow can operate without RWX (ReadWriteMany) storage:
- GUI runs in Read-Only mode
- Configuration files loaded via ConfigMap
- SAP certificate added to an Secret
- Logs written to stdout and stderr (Assumes container output is collected by a monitoring solution)