You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
should there be /usr/src/wordpress instead of /var/www/html, or is that intentional? if so, why does it volume that directory, if that dir is nowhere referenced/used in DOCKERFILE or entrypoint
The text was updated successfully, but these errors were encountered:
See #6 (comment) -- in short, the whole of /var/www/html is the "WordPress-managed" directory. On initial container startup, we copy /usr/src/wordpress into it, and then it's expected that WordPress manages it directly via auto-update / updates through the UI. There are other issues that describe how to circumvent that behavior if you'd like a more "traditional" container experience where WordPress is updated via container redeployments, but I really cannot recommend that (those WordPress auto-updates are your primary line of defense against WordPress security issues).
As for why that specific directory, see the php image we're FROM for details (that's the default directory over there for both Apache and FPM variants).
I am about this line:
wordpress/latest/php8.2/apache/Dockerfile
Line 172 in bd76dc3
should there be
/usr/src/wordpress
instead of/var/www/html
, or is that intentional? if so, why does it volume that directory, if that dir is nowhere referenced/used in DOCKERFILE or entrypointThe text was updated successfully, but these errors were encountered: