Logs and status

berth logs myapp                   # the last 200 lines
berth logs myapp -f                # follow
berth logs myapp --since 30m -n 1000
berth logs myapp --build           # the latest build (or --build 12)
berth logs myapp --release         # the latest release command, i.e. migrations
berth logs myapp --access          # a line per HTTP request
berth logs myapp --cron            # scheduled jobs
berth logs --all -f                # every app at once

Every line has the time and the release that wrote it. Logs live in ~/.berth/apps/<app>/logs/, outlive the containers that wrote them, and roll over at 50 MB.

berth status is the one screen I look at most:

berth v0.1.2 · example.com · berthd up 3d4h
container ✓ running · caddy ✓ up · tunnel ✓ connected (remote) · disk 101.7 GB free · memory 2.2 GB of 16.0 GB committed

APP     STATE    REL  SHA      UPTIME  MEM            PORT  URL                        LAST DEPLOY
myapp   running  v4   b3ab439  2h      131.0 MB/512M  8001  https://myapp.example.com  v4 running 2h ago
blog    running  v12  77ac1f0  3d      58.8 MB/512M   8003  https://blog.example.com   v12 running 3d ago

SERVICE      IMAGE        STATE    MEM       ENDPOINT           LINKED TO  LAST BACKUP
pg:db        postgres:17  running  209.3 MB  192.168.66.1:6001  [myapp]    9h ago

Anything wrong shows up underneath: a crashed app, a database that's down, low disk, memory over 80% committed, a backup that hasn't worked lately. berth status myapp zooms in on one app.

berth events -f       # deploys, crashes, restarts, webhooks and backups as they happen