baseboard
Blog

A page for release day, built from blocks

3 min read

Release day tends to mean six tabs: the host's deploy list, the uptime monitor, the error tracker, the job runner and a couple of log searches. When something breaks you flick between them to line up the times. One page with those views side by side saves the flicking, as long as building it doesn't turn into its own project.

Pages are rows of blocks

A Baseboard page is a stack of rows. Each row holds one to three blocks, and each block is one view: recent deploys, uptime, new errors since release, job runs, recent logs, open pull requests and so on. There are fifteen kinds.

Nobody sets widths. Each kind of block has a weight, and the blocks in a row share its width by weight. Recent deploys weighs two and Uptime weighs one, so in a row together the deploys take two thirds. Rows are always full. If you want a different split, set a block's size to Small, Medium or Large and it replaces the weight.

Start from a template

Workspace owners make pages from New page, which lists templates you can search or filter by category. Two of them are for the bad days.

Release day puts Recent deploys beside Uptime. Under that, new errors sit next to failed job runs, and a full row of logs at the bottom shows errors only.

Incident room leads with Uptime and new errors, gives error logs a row of their own with up to 50 lines, and ends with the last five production deploys beside failed job runs.

The preview next to the list draws the layout and says what the page reads from (hosting, errors, logs). Picking a template copies its blocks into a new page. Later changes to the template don't touch pages already made from it, so moving or removing blocks is safe.

Options come with defaults

Every block has options with defaults, so it works the moment it's on the page. Recent logs can show every line, warnings and errors, or errors only, from 5 to 100 lines. Recent deploys can be limited to production. Job runs shows failed runs unless you untick that.

Each block covers every connection in the project until you narrow it to some groups or connections, so a web app and a worker on different hosts both show up.

Or keep it in your repo

To review layout changes like code, the CLI exports a project's pages as JSON (rows of blocks, each with its type, size, options and connections) and applies them back:

bash
npx baseboard-cli pages export --project <id> > pages.json
npx baseboard-cli pages apply pages.json --project <id>

Applying needs an access token with the Set up scope, made by a workspace owner. The details are in Agents and the CLI. Otherwise, open New page on any project, start from Release day and change what doesn't fit.

More from the blog

See every customer in one place.

Connect a sign-in provider and a billing provider on the free plan. It reads every page and changes nothing.