added optional entrypoint directory

[vutran]

This will add the ability to add additional scripts to be processed (which should be stored in /docker-entrypoint-initwordpress.d/) similar to docker-library/mysql

[yosifkit]

A few questions/comments:

• what is the use case?
• is this the optimal spot to run hooks? should it be after database creation? before modifying wp-config.php? Some users might argue that those other places would be better for hooking in scripts.
• what does this add that couldn't be accomplished with a docker run -d -v /path/to/my-script.sh:/usr/local/bin/apache2-special.sh ... wordpress "apache2-special.sh" (if my script just ends with exec apache2-foreground)?
• the reason for similar directories/hooks in the mysql, postres, mariadb, and percona images is that those are things that need to be run with the database running and so it could not be chained like suggested above.

[vutran]

I can see some use cases for this added functionality:

• cloning a repo with a theme/plugin, and activating it automatically
• running any necessary app-specific tests
• app requirements such as installing composer packages, or compiling assets with node
• pulling uploadable assets from a remote location (wp-content/uploads, etc.)

You're right, we should probably move the script after the database creation should there be any use-case it requires modifications to the db such as changing the home, and siteurl in the wp_options table for different environments such as local, staging, production.

It will enable users to use Docker Compose to bootstrap easily and run any necessary scripts without overriding the default entrypoint