Configuration¶
Paths and limits below are the ones already documented for this Docling
image. /opt/sushi/docs/README.md and /opt/sushi/docs/DEMO.md are the
on-instance notes.
Where things live¶
| Path | What it is |
|---|---|
sushi-docling-api.service |
API service. |
| Port 8443 | HTTPS API. |
~/.config/sushi/docling/access.json |
Account file for ubuntu, mode 0600. |
server.crt beside that file |
TLS certificate for this instance. |
sushi-docling-api |
Helper. It reads the account file and checks TLS without printing credentials. |
/var/lib/docling |
Application state. |
/etc/docling |
Server configuration and the TLS identity. |
/home/ubuntu/.config/sushi/docling |
Client account files. |
/opt/docling and /usr/share/doc/docling |
Installed package and notices. |
Listen address¶
Forward port 8443 with Session Manager. A workstation client needs the certificate and the client credential file copied over an authenticated channel. Keep that credential file readable only by the account that uses it. Do not put credentials in URLs, command arguments, user data, or support logs. Do not disable certificate verification.
Limits¶
PDF and DOCX only, up to 10 MiB per file and 20 PDF pages, one conversion at a time. Use a PDF with selectable text. Scanned pages, image or audio input, embeddings, and a GPU endpoint are outside this package.
Certificate¶
The generated certificate expires after 365 days. Replace it before expiry and update client trust from the instance. Public DNS and automatic renewal are not included.
Do not delete the identity under /etc/docling as a reset.
Last updated November 1, 2026 · Suggest an improvement