Repository navigation
Provide a php dependency only image without wordpress specific files #764
Description
Could it be possible for the WordPress docker image to provide a php dependency only tag variant ?
The regular image currently provides a zip with a version of WordPress and a custom entry point. But you sometimes do not need thoses files and they might also mess your custom setup (for example extracting WP while it shouldn't).
It would be great if this current image is split into 2 stages, one for the php dependencies, and the next one for the wordpress specific files. This should allow me to reuse the wordpress image to build my own docker image ?
I would see maybe a stage around here:
wordpress/latest/php7.4/apache/Dockerfile
Line 123 in 67e960d
We could then have for example:
FROM wordpress:apache-bare
COPY . /var/www/htmlReacted by Gerwin Jansen, Alexander Schomburg and Luiz Petri
Activity
wglambert commentedon Oct 11, 2022
Something like https://github.com/docker-library/docs/tree/master/php#phpversion-apache?
jooola commentedon Oct 11, 2022
I guess that's the idea, but including all the php extensions and settings required/recommended by wordpress.
gerwinjansen commentedon Nov 12, 2022
My goal is to bring my Wordpress based application under version control. I'm using PHP Composer and roots/bedrock to compose my webroot directory and I use a .env file for the settings and secrets.
Next, I want to create a docker image from this webroot directory with a volume for the upload directory and a docker secret for the .env file.
The ultimate goal is to setup a DTAP cycle to deliver my application.
I prefer to use an official docker image from Wordpress so that I don't have to do the maintenance of PHP configuration and extensions myself.
I can replace the
/usr/src/wordpress/with my webroot and I found a workaround for the Entrypoint.But I can't 'undo' the volume of the official image. Hence my support for this request.
Workarounds I can think off:
Both are not very attractive.
jooola commentedon Jan 27, 2023
I used a dirty workaround for now (feel free to propose some improvement):