I’ve pushed up today a container using PHP 5.6 for those that want to use it.
I’d greatly appreciate some feedback as to how that works out for people, as we’ll move to it by default if the feedback is generally good for the 1.8.3 release.
To use these, ensure you are already running 1.8.2 release, and then simply edit the image:
lines in your docker-compose.yml
(or variant) file, and append _5.6
for both the cms-web
and cms-xmr
containers. The cms-db
container is unchanged)
So for example:
version: "2.1"
services:
cms-db:
image: mysql:5.6
volumes:
- "./shared/db:/var/lib/mysql"
restart: always
environment:
- MYSQL_DATABASE=cms
- MYSQL_USER=cms
- MYSQL_RANDOM_ROOT_PASSWORD=yes
mem_limit: 1g
env_file: config.env
cms-xmr:
image: xibosignage/xibo-xmr:release_1.8.2_5.6
ports:
- "9505:9505"
restart: always
mem_limit: 256m
env_file: config.env
cms-web:
image: xibosignage/xibo-cms:release_1.8.2_5.6
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
environment:
- XMR_HOST=cms-xmr
env_file: config.env
ports:
- "80:80"
mem_limit: 1g
Edit your config.env
file, and add lines as follows to the end:
CMS_PHP_POST_MAX_SIZE=4G
CMS_PHP_UPLOAD_MAX_FILESIZE=4G
CMS_PHP_MAX_EXECUTION_TIME=300
That will configure a 4G limit.
Then docker-compose up -d
should switch your PHP version. If you hit issues, removing the _5.6
from both image:
lines, and then docker-compose up -d
should switch you back again.
Please can you also keep an eye on your daily automated backups using this version. It should generate a latest.sql.gz
file each day as before, and also a previous.sql.gz
file, only rotating them if the backup is successful. That addresses the following issue:
We are actively testing for PHP 7, but it’s taking longer than we’d hoped it would, hence this interim solution.