Dev Servers & Logs

Start, stop and restart your dev servers from the Services screen, and follow their logs live.

BifurcSearch requests, mocks and environments…Ctrl PCommandsCtrl KDevelopment

Acme APIWorkspace

Applications

ServicesHealth bar

Routing

Mappings4Proxy rules3CaptureMail

API

Requests12Mocks5Flows1

Workspace

Environments2Vaults1ConfigAudit log

Settings

main2 unpublished changes on this screenPublish

Forward proxy :8080 runningEngine 0.6.0

How it works

Define each dev server once, with its command, folder, port and the vault its secrets come from, and start, stop or restart it from the Services screen or the terminal. Its output streams into a live log you can search or narrow to errors and warnings, and the Logs tab in Capture finds the lines a server printed while it handled a given request. When a port is taken, Free port shows what holds it and stops it.

When to use it

• Start the API, the worker and the front end with one command.
• Find the stack trace behind the 500 you just captured.
• Stop the stray process that still holds port 3000.