Deploy BentoPDF (client-side PDF toolkit) via its Helm chart #48

New issue

Open

opened 2026-08-21 18:51:57 +00:00 by lab · 0 comments

lab commented

2026-08-21 18:51:57 +00:00

Owner

Self-host BentoPDF, a privacy-first,
fully client-side PDF toolkit (merge, split, compress, convert, OCR, sign).
Complements stirling-pdf with client-side processing.

Approach

Upstream ships its own Helm chart in the repo (chart/). Follow the
stirling-pdf pattern:

k3s-ha-cluster/bentopdf/values.yaml + README.md
Chart installed from a git checkout of upstream

Details

Image: ghcr.io/alam00000/bentopdf-simple:latest, container port 8080
Fully client-side processing: no database, no persistence needed
Requires HTTPS for full features (SharedArrayBuffer needed by the
office-to-PDF WASM modules); Caddy TLS covers this

Wiring

Caddy route bentopdf.yukselcloud.com in k3s-ha-cluster/caddy/configmap.yaml
Cloudflare DNS record (covered by the one-click onboarding issue once it lands)

Self-host [BentoPDF](https://github.com/alam00000/bentopdf), a privacy-first, fully client-side PDF toolkit (merge, split, compress, convert, OCR, sign). Complements stirling-pdf with client-side processing. ## Approach Upstream ships its own Helm chart in the repo (`chart/`). Follow the stirling-pdf pattern: - `k3s-ha-cluster/bentopdf/values.yaml` + `README.md` - Chart installed from a git checkout of upstream ## Details - Image: `ghcr.io/alam00000/bentopdf-simple:latest`, container port `8080` - Fully client-side processing: no database, no persistence needed - Requires HTTPS for full features (SharedArrayBuffer needed by the office-to-PDF WASM modules); Caddy TLS covers this ## Wiring - Caddy route `bentopdf.yukselcloud.com` in `k3s-ha-cluster/caddy/configmap.yaml` - Cloudflare DNS record (covered by the one-click onboarding issue once it lands)