Configuration¶
Find the Typesense files, supported scope, and connection settings.
Where things live¶
| Path | What it is |
|---|---|
typesense.service and sushi-typesense-api.service |
Server and gateway. |
| Port 8443 | HTTPS gateway. |
~/.config/sushi/typesense/access.json |
Account file for ubuntu, mode 0600. |
server.crt beside that file |
TLS certificate for this instance. |
sushi-typesense-api |
Helper. It reads the account file and checks TLS without printing credentials. |
| Native API key | Read by the gateway from a server file. Do not print or copy that key into commands. |
/var/lib/typesense |
Application state. |
/etc/typesense |
Server configuration and the TLS identity. |
/home/ubuntu/.config/sushi/typesense |
Client account files. |
/opt/typesense and /usr/share/doc/typesense |
Installed package and notices. |
Limits¶
Single-node text search, filters, and facets. No managed cluster, no high availability, and no preconfigured vector model. CLIP embedding models are not included and are rejected. Native API and peering ports stay on loopback.
Customer requests use sushi-typesense-api. The example collection is in
Getting started. Delete only a test
collection you created, after you have verified it.
Listen address¶
Forward port 8443 with Session Manager. Do not disable certificate
verification. Do not delete /etc/typesense as a reset. The certificate
expires after 365 days.
Last updated November 1, 2026 · Suggest an improvement