Tools
Servers
The curated list: every dev server on the machine, what it is costing you, and the three things you usually want to do to it.
What is in the list#
Servers is the short list — processes that passed one of the three detection signals, with the operating system's own machinery filtered out. That filtering is the feature. A list of everything listening is a list nobody reads.
Reading a row#
Each row is one server. The project name comes from the folder the process was started in rather than the process name, which is why you get acme-storefront instead of four rows all called node.
Memory is shown twice on purpose: a share of the whole machine, and the absolute figure. The share tells you whether it matters; the absolute figure tells you what you get back if you stop it. The reading turns amber once a process is running hot.
Open, copy, kill#
Three things happen to a dev server often enough to be worth a keypress:
- Open
- Launches the server in your default browser at the address it is actually bound to.
- Copy
- Puts that address on the clipboard — for a colleague, a phone on the same network, or a config file.
- Kill
- Stops the process. The port is free by the next scan, five seconds later at the outside.
Elevated processes
A server started from an elevated terminal cannot be stopped by an unelevated app, and Pip does not run elevated. Pip still shows the process and marks it, then tells you plainly that it cannot kill it — rather than offering a button that quietly does nothing.
Finding one row#
Press / and type. Search covers project names, ports and branches together, so you can go looking with whichever of the three you happen to remember.
Did this page not answer it? Tell us what you were looking for — that is how Pip's documentation gets written.