Configuration¶
Find the Whisper CPU files, HTTPS limits, local SDK options, and connection settings.
Where things live¶
| Path | What it is |
|---|---|
sushi-whisper-cpu-api.service |
HTTPS API. |
| Port 8443 | HTTPS API. |
~/.config/sushi/whisper-cpu/access.json |
Account file for ubuntu, mode 0600. |
server.crt beside that file |
TLS certificate for this instance. |
sushi-whisper-cpu-api |
Helper. It reads the account file and checks TLS without printing credentials. |
/opt/whisper-cpu/models |
Bundled model for local SDK calls. |
/var/lib/whisper-cpu |
Application state. |
/etc/whisper-cpu |
Server configuration and the TLS identity. |
/home/ubuntu/.config/sushi/whisper-cpu |
Client account files. |
/opt/whisper-cpu and /usr/share/doc/whisper-cpu |
Installed package and notices. |
HTTPS limits¶
WAV, FLAC, and MP3 with a known duration, up to 10 MiB and five minutes per
clip. One request at a time. int8 CPU inference. Language en or es, or
omit language for automatic detection. No diarization, translation, live
streaming, or voice generation.
The HTTPS example is in Getting started.
Local SDK¶
Version 0.1.10 can pass a WAV, FLAC, or MP3 filename to the installed SDK for a file beyond the HTTPS size or duration limit. That local process uses the bundled model offline. It does not install packages or change the service. Finish API work first, and run one batch at a time. The HTTP limits stay in place.
Versions 0.1.8 and 0.1.9 need an already decoded NumPy audio array for local SDK calls. The direct-filename example requires 0.1.10.
Listen address¶
Forward port 8443 with Session Manager. Do not disable certificate
verification. Do not delete /etc/whisper-cpu as a reset. The certificate
expires after 365 days.
Last updated November 1, 2026 · Suggest an improvement