-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wp-now: Error cases for when the user doesn't stop the server #33
Comments
Hi @flexseth, I've added some clarification below (@adamziel, please correct me if I'm wrong. Don't want to spread misinformation...).
These instructions are only relevant when contributing to WP-NOW.
Nothing :-) It stops: no Docker involved.
You could dig into the specific process in Activity Monitor (under Code/Terminal) and stop it using the UI, but that's both impractical and pointless: once you close the Terminal tab/window (or, in VS Code, for example, either close the window or "Kill" the Terminal), the process shuts down.
Yes, unless you actively stop it (
It launches the same instance in a new port. |
Linking to #31 - Docs for using @ironnysh - Thanks for your notes above, these are solid. I have a few more notes about how the instance starts based on context I'll link for the |
Possible error case
User starts the
wp-now
server viagit clone git@github.com:WordPress/playground-tools.git cd playground-tools nvm use npm install npm run build nx preview wp-now start --path=/path/to/wordpress-plugin-or-theme
Closes VS Code or their editor without stopping the server...
Discovery
What happens if the server isn't stopped?
How to stop the server with Activity Monitor or Task Manager (Windows), Linux
Server is constantly running in the background?
What happens if they try to open the VS Code extension in this same folder as
wp-now
is running?The text was updated successfully, but these errors were encountered: