Print generated content to thermal receipt printers.

Quickstart

From a local checkout, install with Cargo, check the machine, find a printer, and print a Markdown file. Do not install the crates.io or npm packages. Those are old snapshots.

cargo install --path . --force

slipbridge doctor --json
slipbridge printers list --json
slipbridge print ./ticket.md \
  --printer tcp://epson-m30:9100 \
  --paper 80mm \
  --json

Use --printer with a discovered printer id, a tcp:// endpoint, or a usb:// selector.

Print content

Slipbridge can print a file directly or render it first. Use render when you want the PNG that will be sent to the printer.

slipbridge print ./receipt.png --type image \
  --printer tcp://epson-m30:9100 --paper 80mm

slipbridge print ./ticket.md --type markdown \
  --printer tcp://epson-m30:9100 --paper 80mm

slipbridge print ./note.txt --type text \
  --printer tcp://epson-m30:9100 --paper 80mm

slipbridge render ./ticket.md \
  --output preview.png --paper 80mm

Templates

Templates use Handlebars syntax. Pass a JSON input file with --template to render structured data before printing.

slipbridge print ./order.json \
  --template ./pickup.hbs \
  --printer tcp://epson-m30:9100 \
  --paper 80mm

{
  "name": "Avery",
  "subtitle": "Pickup shelf 4"
}

# {{name}}

{{subtitle}}

Connect printers

Start with discovery, then inspect the selected printer when you need the resolved driver and capabilities. The hardware path we have actually used is an Epson TM-m30II-H.

slipbridge printers list --json
slipbridge printers inspect \
  --printer tcp://epson-m30:9100 \
  --json
slipbridge printers test \
  --printer tcp://epson-m30:9100 \
  --json

Automation

Add --json when another process needs to read results. Use the structured fields instead of parsing human output.

slipbridge print ./ticket.md \
  --printer tcp://epson-m30:9100 \
  --paper 80mm \
  --json

Queueing

Queueing is useful when more than one process may print to the same device. Slipbridge writes a job to disk, then a worker sends queued jobs while holding a per-printer lock.

slipbridge print ./ticket.md \
  --printer tcp://epson-m30:9100 \
  --paper 80mm \
  --enqueue \
  --json

slipbridge jobs list --json
slipbridge jobs inspect --job <job-id> --json
slipbridge jobs cancel --job <job-id> --json
slipbridge jobs run --once --json

Queue state lives in the platform data directory by default. Set SLIPBRIDGE_STATE_DIR when you want an isolated queue for tests or development.

Printer defaults

Defaults keep repeated commands short. They are stored locally in printers.toml, so a script or agent can use the same settings as a human operator.

slipbridge printers defaults set \
  --printer tcp://epson-m30:9100 \
  --paper 80mm

slipbridge printers defaults show \
  --printer tcp://epson-m30:9100 \
  --json

Troubleshooting