Skip to main content
Upstream source: Current installation guide. Typesense stores collections under /data; no separate SQL Datastore is needed. Keep its administration API private and the master key server-side. Public search clients should use a restricted search-only key.

Towbar manifest

.towbar/services/typesense.service.yml

Configure

  1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP. Commit the manifests, then sync the repository and inspect the resolved configuration.
  2. Set the Service’s declared runtime values under Service → Settings → Secrets using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
  3. Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
  4. This manifest has no public domain. Use a trusted connection to the server for the first check. Add a public route only after configuring the product’s authentication or an access gateway.
  5. Deploy the Service, then perform the checks below before enabling auto-deploy.

Runtime values

Save these values on the Service after the repository sync. The manifest declares required keys, not their values.

Verify

From an authorized client on the application network, create a collection, index a document, query it, and confirm the collection survives redeployment. For field constraints, see Service manifest.
Last modified on September 27, 2026