serve
runbooks serve
Section titled “runbooks serve”This command is intended for developers of Runbooks.
Use runbooks serve to start the backend API server without starting the frontend server or opening the browser.
runbooks serve <path-to-runbook> [flags]Arguments
Section titled “Arguments”<path-to-runbook>- Path to a directory containing therunbook.mdxfile, or to the file itself.
--working-dir <path>- Base directory for script execution and file generation (default: current directory)- All relative paths are resolved from this directory
- Can be absolute or relative to current directory
--working-dir-tmp- Use a temporary working directory (automatically cleaned up on exit)- Useful for isolated testing or sandboxed execution
- Overrides
--working-dirif both are specified
--output-path <path>- Directory where generated files will be written (default:generated)- Resolved relative to the working directory
--no-telemetry- Disable anonymous telemetry. Can also be set viaRUNBOOKS_TELEMETRY_DISABLE=1environment variable.
What it does
Section titled “What it does”When you run runbooks serve:
- Starts the Backend Server - Launches a Go-based HTTP server on port 7825
- Serves the API - Provides REST endpoints for the frontend to call
- Does NOT Open Browser - You must manually navigate to
http://localhost:7825or run the frontend separately
Development workflow
Section titled “Development workflow”Here’s a typical development workflow:
-
Start the backend:
Terminal window runbooks serve testdata/demo-runbookOr if you want to easily re-compile the backend:
Terminal window go run main.go serve testdata/demo-runbook -
In another terminal, start the frontend:
Terminal window cd webbun dev -
Open your browser to
http://localhost:5173(Vite’s port) -
Make changes to:
- React code in
/web/src- hot reloads automatically - Go code - restart the
servecommand - Runbook files - refresh the browser
- React code in