Switch to roots/wordpress and WP Packages#470
Open
retlehs wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This switches the template from
johnpbloch/wordpress-coretoroots/wordpressand from WPackagist to WP Packages. Submitted as a community contribution per the README's "you are welcome to contribute" note, in case anyone forking or referencing this template would benefit from a current state.Disclosure: I maintain WP Packages and Bedrock.
Why
The current template uses two paths that have aged:
johnpbloch/wordpress-core— still maintained, but Roots' equivalent is now the more featureful and ecosystem-aligned defaultWPackagist vs WP Packages
metadata-urljohnpbloch/wordpress-corevsroots/wordpressjohnpbloch/wordpress-coreroots/wordpressroots/wordpress,-full,-no-contentroots/wordpress-full)johnpbloch/wordpress-core-installer ^2.0)roots/wordpressChanges
composer.json— dependencies:https://wpackagist.org→https://repo.wp-packages.orgjohnpbloch/wordpress-core-installer+johnpbloch/wordpress-corewith a singleroots/wordpress: ^6.0(the meta-package pulls in the installer transitively, so no separate require is needed)wpackagist-plugin/akismet→wp-plugin/akismettwentytwentyone,twentytwentytwo,twentytwentythree) and addedwp-theme/twentytwentyfive(current WP default)allow-pluginsto allowroots/wordpress-core-installer>=5.6.20→>=8.0(matches the actual Platform.sh runtime in.platform.app.yaml)extra.wordpress-install-dir: wordpressto ensure the install directory matches the existinginstaller-pathslayoutcomposer.json— package metadata:The package was previously named
johnpbloch/wordpresswith WordPress.org description, homepage, authors, and Trac/forum/IRC support links — all inherited from when the template was a fork of johnpbloch's package. Since this template is no longer that fork, the metadata is now updated to actually describe what it is:name:johnpbloch/wordpress→platformsh-templates/wordpress-composerdescription: WordPress.org boilerplate → "Platform.sh starter template for deploying WordPress via Composer."homepage: wordpress.org → the repo URLtype:package→project(standard for a deployable site template)keywords: addedcomposerandplatformsh; droppedblogauthorsblock (was claiming "WordPress Community")support: simplified from WordPress.org Trac/forum/IRC to the repo's GitHub issues + sourcecomposer.lock: regenerated (5 installs / 8 updates / 6 removals)README.md: updated prose references from the johnpbloch fork toroots/wordpress; bumped "PHP 7.4" to "PHP 8.1" (the actual deployed runtime); "WPackagist" → "WP Packages"Notes
I'm aware this repo is marked "no longer maintained" — opening this anyway in case it's useful for forks or anyone referencing the template. Companion PR: a similar refresh on
platformsh-templates/wordpress-bedrock#1010, which had the same staleness pattern. Also related: a docs PR onplatformsh/platformsh-docs#5557updating the WordPress Composer guides.Open to feedback. Happy to close if it's not the direction you want.