[wp-trac] [WordPress Trac] #63543: Environment variable WP_CONFIG_PATH should be to cli container in wordpress-develop env

WordPress Trac noreply at wordpress.org
Sat Jun 7 00:21:27 UTC 2025


#63543: Environment variable WP_CONFIG_PATH should be to cli container in
wordpress-develop env
-------------------------------------------------+-------------------------
 Reporter:  westonruter                          |       Owner:
                                                 |  westonruter
     Type:  enhancement                          |      Status:  accepted
 Priority:  normal                               |   Milestone:  6.8.2
Component:  Build/Test Tools                     |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback has-test-     |     Focuses:
  info                                           |
-------------------------------------------------+-------------------------
Changes (by SirLouen):

 * keywords:  has-patch => has-patch dev-feedback has-test-info


Comment:

 == Combined Reproduction and Test Report
 === Description
 ✅ This report validates that the indicated patch works as expected.

 Patch tested: https://github.com/WordPress/wordpress-
 develop/pull/8931.diff

 === Environment
 - WordPress: 6.9-alpha-60093-src
 - PHP: 8.2.28
 - Server: nginx/1.27.5
 - Database: mysqli (Server: 8.4.5 / Client: mysqlnd 8.2.28)
 - Browser: Chrome 137.0.0.0
 - OS: Windows 10/11
 - Theme: Twenty Twenty-Five 1.2
 - MU Plugins: None activated
 - Plugins:
   * Test Reports 1.2.0

 === Reproduction Steps
 1. Set up the Gutenberg plugin inside `wordpress-develop` plugins
 directory
 [https://gist.github.com/westonruter/631424e1b7f387a28c349c35437aaf15 with
 the given instructions]
 2. Run `npm run env:cli -- wp post create --post_type=post
 --post_title="Sample" --post_content="Sample" --post_excerpt="Sample"`
 3. 🐞 Error reproduced `Warning: Constant WPINC already defined in
 /var/www/src/wp-settings.php on line 21`

 === Expected Result
 - `wp-cli` runs as normal

 === Actual Results
 1. ✅ Issue resolved with patch.

 {{{
 > WordPress at 6.9.0 env:cli
 > node ./tools/local-env/scripts/docker.js run --rm cli wp post create
 --post_type=post --post_title=Sample --post_content=Sample
 --post_excerpt=Sample

 [+] Creating 2/2
 Success: Created post 8.
 }}}

 === Additional Notes
 Ngl, I was curious about this setup, so I took the opportunity to test it
 with the corresponding report.

 PS: Although this looks good, I still feel that if this docker env was
 only meant for GHA, all these "improvements" are not relevant (as
 theorically it was not relevant to add images for mailhog/ftp server,
 similarly for testing purposes).

 So I was wondering: maybe a lando image could serve to run parallelly, for
 example, the mailhog server without having to mess the `docker-
 composer.yml` and `install.js` files?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63543#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list