wp-env: Fix issue where docker & wp had different URLs #20228
Merged
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.
Description
Fixes an issue where a custom port in .wp-env.json would not change the URL used to install WordPress. This resulted in the WordPress redirecting you to the default port. So if you would access docker at localhost:4013, it would send the request to WordPress, which thought the URL was localhost:8888, and you'd then be redirected to localhost:8888 which had nothing running on it.
How has this been tested?
I made sure that accessing the custom port in .wp-env.json correctly loaded WordPress on that port. I also added unit tests to verify that environment variables are validated and take precedent over config values.
Types of changes
Bug fix
Checklist: