env: Add support for dynamic URLs and allow setting WP_HOME and WP_SITEURL via env variables

[USERSATOSHI]

What?

Closes #23947, #65008

Why?

Currently the wp-env site is set to localhost address, so trying to map the site to the likes of an ngrok external domain just results in a redirect back to localhost.(#23947)

This PR adds support for that by dynamically defining the WP_HOME and WP_SITEURL via the snippet sent by @glendaviesnz.

Alongside this PR also adds support for setting WP_HOME and WP_SITEURL via env variables to allow for cases where the url is generated dynamically like gitpod.

How?

This PR solves this by adding WP_ENV_DYNAMIC_URLS_ENABLED env var ( default to true ) which enables dynamically defining WP_HOME and WP_SITEURL constants.
This PR also adds WP_ENV_HOMEURL , WP_ENV_SITEURL for development environment and WP_ENV_TESTS_HOMEURL , WP_ENV_TESTS_SITEURL for tests environment.

to disable dynamically defining , pass WP_ENV_DYNAMIC_URLS_ENABLED=false when running wp-env start.

Testing Instructions

_

1. run npm run wp-env start -- --update
2. run a tunnel ( npx localtunnel -p 8888 )
3. open the tunnel domain
4. see the site working as normal.

Screenshots or screencast

npm run wp-env start -- --update

WP_ENV_DYNAMIC_URLS_ENABLED=false npm run wp-env start -- --update

WP_ENV_SITEURL & WP_ENV_HOMEURL support

cmd: WP_ENV_HOMEURL="https://tricky-boats-post.loca.lt" WP_ENV_SITEURL="https://tricky-boats-post.loca.lt" npm run wp-env start -- --debug --update

Note: --update is required because it needs to write to wp-config.php.

[USERSATOSHI]

Trying to figure out why setting url via env is causing
~~ ~~⠙ Configuring WordPress.Error: This does not seem to be a WordPress installation.~~ ~~The used path is: /var/www/html/~~ ~~Pass --path=`path/to/wordpress` or run `wp core download`.~~ ~~⠹ Configuring WordPress.exit status 1~~ ~~⠸ Configuring WordPress. Container 23f76220ed5a7267362fb06fbba395ea-mysql-1 Running~~ ~~ Container 23f76220ed5a7267362fb06fbba395ea-wordpress-1 Running~~ ~~

If I figure it out, then I will add the fix else, I will remove the env support. I believe that dynamically defining should also partially fix issue #65008

UPDATE: fixed the issue by changing the env from WP_ENV_HOME to WP_ENV_HOMEURL, didn't realize, it was being used for WordPress installation.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @apeatling, @jdmwood.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: apeatling, jdmwood.

Co-authored-by: USERSATOSHI <tusharbharti@git.wordpress.org>
Co-authored-by: Mwalek <mwalek@git.wordpress.org>
Co-authored-by: glendaviesnz <glendaviesnz@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.