Skip to content
Get Started

Server Overview

Assets, tasks and the cache work on one machine with no server. barca serve is the same binary run as a long-lived process: it fires schedules, serves an HTTP API and a web UI, and can hold one record of results and runs for a whole team. Start it in a project with:

barca serve # 127.0.0.1:8274 (--host 0.0.0.0 for other machines)

Authentication is off by default (Authentication and Tokens).

I want to… Read
Run assets, tasks or sensors on a cron schedule Scheduling With Cron
Give a team one cache and one run history Share Results With a Team
Run it as a service: a container, systemd, behind nginx or Traefik Deploying barca serve
Understand how laptops and the server share results, and what --server does Server Mode
Manage the run queue, restarts, stop grace, capacity and run timeouts Operating barca serve
Start runs and read results from code, over HTTP or with the Python client Server API
Post to Slack when a job starts failing or recovers Slack Alerts
Send traces and metrics to Datadog Telemetry
Require tokens, and connect the web UI and laptops with them Authentication and Tokens
See what the web UI shows and does The Web UI
See every flag of the command barca serve

A first setup usually goes Scheduling With Cron (if you need schedules), then Share Results With a Team (if more than one person runs barca), then Deploying barca serve.

Authentication is off by default. barca serve --auth token requires a token on every API request; barca tokens bootstrap prints a one-use code that connects the web UI, where you create tokens for laptops and scripts. The steps are in Authentication and Tokens.