Opened 12 months ago
Last modified 10 months ago
#63886 new enhancement
Simplify the steps for getting a local environment started
| Reported by: | jorbin | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Build/Test Tools | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
Currently, the instructions for getting started are hard to follow. They require you to manually check for prerequisites on your machine and run 4 separate commands. Some of these steps can be simplified.
Change History (5)
This ticket was mentioned in Slack in #core by jorbin. View the logs.
12 months ago
This ticket was mentioned in Slack in #core by wildworks. View the logs.
11 months ago
#4
@
11 months ago
This ticket was featured in 6.9 Bug Scrub today.
Slack Link: https://wordpress.slack.com/archives/C02RQBWTW/p1759744031922919
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
I am envisioning two things: First is a new script in tools/local-env that checks for prerequises and reports failures in a friendly manner.
The second is a change to package.json so that a new
npm run getstartedcommand which will run the preflight check from step one and the other which does the steps from https://github.com/WordPress/wordpress-develop/blob/f40b60d4b2f00e6342753df4a1dc247fc99e286c/README.md#to-start-the-development-environment-for-the-first-timeIt could also potentially call another new script which would print out some friendly info such as the username:password and links to make/core