[wp-trac] [WordPress Trac] #63543: Environment variable WP_CONFIG_PATH should be set on cli container in wordpress-develop env
WordPress Trac
noreply at wordpress.org
Sat Jun 7 08:42:14 UTC 2025
#63543: Environment variable WP_CONFIG_PATH should be set on 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 |
-------------------------------------------------+-------------------------
Comment (by SirLouen):
Replying to [comment:5 westonruter]:
> For the longest time I've used this Docker environment as my development
environment.
The only good thing is that these gimmicks don't affect GHA in any regard:
```
wp_cli( `config create --dbname=wordpress_develop --dbuser=root
--dbpass=password --dbhost=mysql --force --config-
file=${process.env.LOCAL_DIR}/../wp-config.php` );
```
Anyway, for example, I had a couple of things going locally
https://core.trac.wordpress.org/ticket/63135 (finished)
https://core.trac.wordpress.org/ticket/63172 (finished)
https://core.trac.wordpress.org/ticket/63336 (WIP)
https://core.trac.wordpress.org/ticket/63421 (WIP)
Because testing under any of these conditions have been a thing several
times for me in the past weeks.
> It's not my understanding that it was ever only intended for GHA. The
readme provides instructions on how to use it for local development.
Thing here is that I commented about this during a `dev-chat` and that was
the answer. This is why I'm looking how maybe a lando spinoff could make
the trick.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63543#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list