docker-library / docker-library/wordpress
Include WP-CLI in all WordPress images
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
For a while now, WP-CLI has become the official way to manage WordPress from scripts / command line.
But if you glance through docker-entrypoint.sh, the current way of installing WordPress and hacking wp-config.php with sed and awk is not pretty and error-prone compared to a bunch of WP-CLI commands like
wp core download
wp config set
wp core install
WP-CLI doesn't take too much space, and it's become essential. I propose to:
- include
WP-CLIin all official WordPress images, - deprecate the stand-alone
WP-CLIimage, - refactor
docker-entrypoint.shusingWP-CLI.
It will show the community the relevant way of managing WordPress from the command line, and will make it easier to actually use the image later on. It will also solve #256.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker-entrypoint.sh and review how the current image installs WordPress and edits wp-config.php with sed and awk. Compare those steps with the proposed WP-CLI commands, then inspect how the standalone WP-CLI image is represented. Done means WP-CLI is included in all official WordPress images, the entrypoint uses it for setup, and the standalone image is deprecated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100