Skip to content

feat: replace WP Starter with SymPress Runtime - #29

Merged
brianvarskonst merged 8 commits into
mainfrom
feat/runtime-migration
Sep 30, 2026
Merged

brianvarskonst merged 8 commits into
mainfrom
feat/runtime-migration

Conversation

@brianvarskonst

@brianvarskonst brianvarskonst commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

Runtime migration review

The project replaces WP Starter with sympress/runtime. Its configuration is dev-ops/runtime.json; compatibility is disabled and dotenv local overrides remain explicitly disabled to preserve the existing two-file convention. The command provider uses the injected environment reader and database status from Runtime preflight. The base MU package declares kernel boot ownership.

The dependency follows Runtime main in its private repository; the lockfile pins merged commit 60249ee25ead52f94e2b83e9be4ce472cd3b2fcf. All six implementation PRs and review corrections #7 are merged. Private repository access is required through SSH or Composer GitHub authentication. WP-CLI is the independently executed, SHA512-verified root phar; removing the Composer WP-CLI bundle avoids its conflict with Symfony Process 8.1 while retaining all commands.

Public WordPress URLs remain at the site root: WP_SITEURL=${WP_HOME}. The original DDEV Nginx rules map public endpoints to the physical public/wp core directory. No Nginx routing changes are required by this migration. The starter setup command and documentation use the same root URL.

Verification in a fresh DDEV project with a separate database:

  • Composer install and WordPress installation succeeded; direct and locked package graphs contain no wecodemore/* dependency.
  • QA passed: 7 tests, 49 assertions, coding standards and static analysis, including the root-URL setup regression.
  • The standalone doctor, bin/console doctor --json and wp console doctor --json report 14 passing checks.
  • The kernel boots once; wp console debug:container succeeds.
  • Browser smoke verified a successful homepage response, the root /wp-login.php form action and authenticated root /wp-admin/ dashboard with no JavaScript errors.

Reproduce with ddev composer install, ddev composer qa, ddev exec php bin/console doctor --json, and ddev exec php wp-cli.phar console debug:container. Runtime's tools/consumer-smoke.mjs performs the browser checks using the private local environment credentials. WP-CLI 2.12 can print upstream PHP 8.5 deprecations; use the standalone doctor for clean machine-readable JSON.

Repeated Composer installation, global composer install --no-plugins and the standalone runner preserve 575 generated file hashes/link targets on the reviewed revision. Runtime restores the standard WordPress package layout and Composer autoload metadata before loading project code. QA and root-URL browser smoke pass again with this lockfile. Runtime's mandatory integration and differential job passes all 1,059 tests / 7,365 assertions without skips, the evidence check for 407 rows and 251 differential cases. Its real WPackagist installation job also passes. The previous CI authentication blocker is resolved by the read-only deploy key described below. Successful consumer CI is required before merge; Runtime's documented offline recovery boundaries still apply.

Existing uncommitted changes in the original checkout were preserved by implementing this migration in a separate Git worktree. Generated configuration, local credentials and browser sessions are not committed.

The project owner approved enabling deploy keys for SymPress. A repository-scoped, read-only Runtime key now supplies COMPOSER_SSH_KEY to the consumer workflows; COMPOSER_SSH_KNOWN_HOSTS pins GitHub's published host keys. The workflows are pinned to the reviewed SSH-support commit. CI must pass with that access before merge. When updating an existing environment from a previous /wp URL, run vendor/bin/sympress-runtime flush-env-cache so cached values cannot retain that URL.

@brianvarskonst
brianvarskonst marked this pull request as ready for review September 30, 2026 11:07
@brianvarskonst
brianvarskonst merged commit e208e87 into main Sep 30, 2026
3 checks passed
@brianvarskonst
brianvarskonst deleted the feat/runtime-migration branch October 6, 2026 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant