Module Page Bug 1.8.8

Peter · April 13, 2018, 12:28pm

New Docker containers that have the fix included are now live.

You will need to open your docker-compose.yml or cms_custom-ports.yml depending which one you are using.

Then edit this line:

xibosignage/xibo-docker/blob/master/docker-compose.yml#L23


    mem_limit: 1g
    env_file: config.env
cms-xmr:
    image: xibosignage/xibo-xmr:release-0.7
    ports:
        - "9505:9505"
    restart: always
    mem_limit: 256m
    env_file: config.env
cms-web:
    image: xibosignage/xibo-cms:release-1.8.8
    volumes:
        - "./shared/cms/custom:/var/www/cms/custom"
        - "./shared/backup:/var/www/backup"
        - "./shared/cms/web/theme/custom:/var/www/cms/web/theme/custom"
        - "./shared/cms/library:/var/www/cms/library"
        - "./shared/cms/web/userscripts:/var/www/cms/web/userscripts"
    restart: always
    links:
        - cms-db:mysql
        - cms-xmr:50001

change the release-1.8.8 to latest ie that line should read

image: xibosignage/xibo-cms:latest

To pull the new containers you’d down the docker

docker-compose down

then run

docker-compose pull
docker-compose up -d

with the -f flag if you’re using a custom compose file (custom ports, remote mysql etc).

ie for example:

docker-compose -f cms_custom-ports.yml pull
docker-compose -f cms_custom-ports.yml up -d

Too all our Cloud Hosting users, this fix is already live in our Cloud.