WP-CLI as a backend for steps
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the linked WP-CLI command documentation and the discussion about plugins, downloads, and shell commands. Done means reaching and documenting an agreed, bounded integration scope for Blueprint steps rather than exposing every WP-CLI command.
Written by the indexing model from the issue text.
Description
How many of WP-CLI commands could Blueprints reuse instead of reinventing the same logic?
- plugin install
- Could potentially power the installPlugin step
- Accepts a plugin slug, a path to a local zip file, or a URL to a remote zip file.
- config set – could power the defineWpConfigConsts step
- core multisite-convert – could power the enableMultisite step
- config shuffle-salts
- export and import – could handle WXR processing
- language – we could support installing language packs
- server – could potentially run the server on native PHP and maybe in Node.js
- theme, plugin, user
- scaffold post types, taxonomies etc code generation
Discussion
- Should all Blueprint steps become just plugins to wp-cli?
- No, simple steps like cp, mv etc don't warrant loading the entire wp-cli machinery and could be handled higher up in the stack.
- Should all wp-cli commands be available as Blueprint steps?
- It seems like a bad idea. This would inflate the scope, tightly couple the Blueprint library to wp-cli, and require inventing ways to express shell commands as JSON.
- Let's handle all downloads outside of WP-CLI. WP-CLI is sequential in nature (download plugin X, then download plugin Y), and Blueprints need to parallelize the downloads (download plugins X and Y at the same time).
cc @schlessera @swissspidy @danielbachhuber
- Dominant language
- PHP
- Stars
- 61
- Forks
- 22
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from WordPress/php-toolkit
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WordPress/php-toolkit#313 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
WordPress/php-toolkit#306 ·
-
WPCS complianceOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
WordPress/php-toolkit#157 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WordPress/php-toolkit#138 · 7 comments · 2 reactions ·
-
[Blueprints v2] Constraint the Blueprint bundle formatMay be free again @JanJakes claimed this 430 days ago, and no pull request is open. OpenBlueprints enhancement
WordPress/php-toolkit#132 · 4 comments · 1 assignee ·
All issues in WordPress/php-toolkit
Similar issues
-
bug status: unverified
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
0. needs triage bug developer experience manual: developer
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
nextcloud/documentation#15690 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Icinga/icinga-kubernetes-web#181 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rubenarslan/formr.org#708 ·