Make wp-content/ and wp-config.php overwrite optional

[drzraf]

So that

• wp-content is mountable, and even moutable read-only (Adding custom theme and plugins #115, add a VOLUME to wp-content/ #6, avoid tar extraction failure if wp-content is bind-mounted read-only #281)
• wp-config.php is mountable (Configure all wp-config.php variable with Docker environment variables ? #200, wp-config.php mounting issue #231, Not able to mount file (e.g. wp-config.php) #135, Allow users to set additional configuration options #8, Inject configuration using environment variable #142, Hook in to specific point in entrypoint script #147)

[tkaymak]

Any update on this?

[cyrilchapon]

up

[ConstantinElse]

When this PR is going to be accepted ? I need it too.

[joshbetz]

In my image, I'm putting the main config in wp-config.php and auto-loading from another directory.

https://github.com/joshbetz/docker-wordpress/blob/master/fpm/wp-config.php#L3-L5

You can see how I'm using it here: https://github.com/joshbetz/docker-wp/blob/master/docker-compose.yml#L24

https://hub.docker.com/r/joshbetz/wordpress/

[tianon]

Sorry for the long delay 🙇

The majority of the desired functionality here has been accomplished without any explicit environment variable through a combination of #206, #351, and (much more recently) #507.

• Adjust "wp-config.php" behavior to be skipped if configuration is not provided #206: no touching of wp-config.php unless we have variables set that imply we should
• Add "--no-overwrite-dir" to "tar" invocation for running as an arbitrary user #351: tar --no-overwrite-dir
• Exclude existing "pluggable" content in case it's been updated #507: exclude copying of wp-content directories which already exist

That last one isn't exactly what's asked for here, but I think it's pretty reasonable: the test isn't at all deep (just a directory existence check), so if you don't want to actually have the default themes/plugins, you can just pre-create the relevant directories (empty) and copying them will be skipped.