Docs: add info on how to connect to the WP ENV MySQL database #31975
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
getdave
added
[Type] Developer Documentation
talldan
approved these changes
May 19, 2021
|
Size Change: 0 B Total Size: 1.62 MB ℹ️ View Unchanged
|
jeyip
approved these changes
May 19, 2021
getdave
force-pushed
the
update/add-details-on-accessing-wpenv-database
branch
from
41259c7 to
0c362ca
Compare
|
Thanks all 🍾 Will merge once rebase gets the tests to pass. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Currently there doesn't appear to be any info on how you can access the MySQL database running on the
wp-envinstance.This PR documents the process for gaining access.
Hat tip to @jeyip for the original information on how to do this and @noahtallen for pointing me in the right direction.
How has this been tested?
wp-envfor your local setup.Screenshots
Types of changes
New feature (non-breaking change which adds functionality)
Checklist:
*.native.jsfiles for terms that need renaming or removal).