I would assume, correct me if i'm wrong, that the confusing part is the fact that the volume is mounted on both the wordpress and nginx containers...
Thank you for explaining this, but this was actually not my confusion. I am confused about what the directory would actually hold.
The reason that the wordpress directory exists on the host machine is to maintain the state of the WordPress docker container should it shutdown (this also goes for the mysql directory).
Would this mean that the wordpress directory on the host machine already contains files ? Or would the modified / uploaded files be placed in there?
As for the rest of your feedback, thank you for clarifying. I will get to work with this in the next few days so I'll let you know how far it gets me.
The wordpress volume on the host machine holds the core WordPress files for the WordPress container (wp-config.php, wp-content/, wp-admin, etc.). Those files initially come from the WordPress container itself, when it's built. Since the wordpress volume is mounted to the container, from the host, you can do whatever you want with the files and they will propagate over to the container.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So, I've read your feedback, thanks for this!
Thank you for explaining this, but this was actually not my confusion. I am confused about what the directory would actually hold.
Would this mean that the wordpress directory on the host machine already contains files ? Or would the modified / uploaded files be placed in there?
As for the rest of your feedback, thank you for clarifying. I will get to work with this in the next few days so I'll let you know how far it gets me.
Thank you!
The
wordpressvolume on the host machine holds the core WordPress files for the WordPress container (wp-config.php,wp-content/,wp-admin, etc.). Those files initially come from the WordPress container itself, when it's built. Since thewordpressvolume is mounted to the container, from the host, you can do whatever you want with the files and they will propagate over to the container.