WordPress and Docker

(it is version controlled), since that theme is in a volume, a change to that theme will not be a change to “the content of the docker image” and so will not trigger an image re-build (in an automatic setup, but even if it did, it would not have an effect on the image). So I don’t know in this scenario, how new changes to the theme can be reflected to the production server.

I am in the same scenario as well right now. This is my development flow:

1. Work on my local development site.
2. Test the changes. If everything works well, I push to my repository (dev)
3. Review changes. If nothing breaks, merge with production/main branch
4. On my server, pull the changes from production/main.
5. Rebuild the docker image. (Database is in its own docker container, so it won’t be affected by this).

git-ignored most WordPress core files from the git repository

That’s how I usually do it, so that I can safely migrate to another container (if required)

Using other means such as npm install and wp core install and even sometimes “uploading” some files (probably could be made much less painful with Ansible) manually and so on… to get it “started”. May I know how you take this initial step as well?

For the first time, it depends of your preference. For example, I tell the dockerfile to install composer or npm, but I install the packages/libraries/dependencies manually by using the container bash. I’ve seem others that add all of the commands in the Dockerfile.