Deploying ContentManager as docker container

Load Image

Use the file dpe-contentmanager.tar.gzip from the delivery folder to load the image

docker load < dpe-contentmanager.tar.gzip

Prepare settings.json

Copy the file settings.json from the delivery sub folder webapp to a location where it can be used from docker, e.g. /etc/cm/

Adapt settings.json to connect to your DPE Services, see Preparing settings.json

Create Container

docker run -p 80:80 --name content-manager --mount type=bind,source=/etc/cm/settings.json,target=/usr/share/nginx/html/settings.json dpe-contentmanager:latest 

• Option -p <externalPort>:80 specifies which external port to use, the container internal port is always 80

• Option --mount injects/maps the settings.json file from the host location to the inside of container

Docker Compose

Alternatively you can also use a docker compose file

compose.yaml

version: '3.7'
services:
  dpe_cm:
    container_name: cm
    image: docker-registry.davidsystems.com/dpe-contentmanager:latest
    restart: always
    ports:
      - 80:80
    volumes:
      - /etc/cm/settings.json:/usr/share/nginx/html/settings.json            

HTTPS

The ContentManager container is supporting HTTP.

Typically, in enterprise environments a HTTPS-offloading proxy is used to route the HTTPS traffic from the outside to an internal docker container.