Manticore Search — a fast, open-source search engine: full-text search, filtering, faceting, autocomplete, and vector search, with a MySQL-compatible SQL interface and an HTTP/JSON API (an Elasticsearch alternative). Deployed as a host-networked Nomad service with a persistent data volume.
Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.
Source ↗ Project ↗ ★ 12k ⚑ Report an issue
Save as values.hcl, edit, then run:
# The name of the Nomad job.
job_name = "manticore"
# The Nomad namespace to deploy into.
namespace = "default"
# The datacenters to deploy to.
datacenters = ["*"]
# The Manticore Search container image. Pin a tag in production.
image = "manticoresearch/manticore:latest"
# Host port for the MySQL-compatible SQL interface.
sql_port = 9306
# Host port for the HTTP/JSON API.
http_port = 9308
# Host port for the binary protocol (inter-node / replication).
binary_port = 9312
# Named volume for Manticore data (/var/lib/manticore): all tables and indexes.
data_volume = "manticore_data"
# Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []
# Resources for the Manticore task. Large indexes benefit from more memory.
resources = {
cpu = 500
memory = 512
}
| Name | Type | Default | Description |
|---|---|---|---|
| job_name | string | "manticore" | The name of the Nomad job. |
| namespace | string | "default" | The Nomad namespace to deploy into. |
| datacenters | list | ["*"] | The datacenters to deploy to. |
| image | string | "manticoresearch/manticore:latest" | The Manticore Search container image. Pin a tag in production. |
| sql_port | number | 9306 | Host port for the MySQL-compatible SQL interface. |
| http_port | number | 9308 | Host port for the HTTP/JSON API. |
| binary_port | number | 9312 | Host port for the binary protocol (inter-node / replication). |
| data_volume | string | "manticore_data" | Named volume for Manticore data (/var/lib/manticore): all tables and indexes. |
| constraints | list | [] | Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true". |
| resources | object | {
cpu = 500
memory = 512
} | Resources for the Manticore task. Large indexes benefit from more memory. |
No variables match.
This pack stores data in one Docker named volume:
manticore_data
restic
# Run on the node hosting this pack. Point restic at your repo first: # export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>" # export RESTIC_PASSWORD="<repo-password>" # export AWS_ACCESS_KEY_ID=<key> AWS_SECRET_ACCESS_KEY=<secret> restic backup \ /var/lib/docker/volumes/manticore_data/_data
rclone (sync to S3/R2)
rclone sync /var/lib/docker/volumes/manticore_data/_data backup:<bucket>/manticore_data
Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.
Manticore Search — a fast, open-source search engine. Full-text search, filtering, faceting, autocomplete/suggestions, and vector search, exposed through a MySQL-compatible SQL interface and an HTTP/JSON API. A lean Elasticsearch alternative that's easy to run and query.
Single host-networked Nomad service with a persistent data volume.
nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run manticore --registry=nomploy
| Variable | Default | Description |
|---|---|---|
sql_port |
9306 |
MySQL-compatible SQL port. |
http_port |
9308 |
HTTP/JSON API port. |
binary_port |
9312 |
Binary protocol (inter-node/replication). |
data_volume |
manticore_data |
/var/lib/manticore — all tables and indexes. |
image |
manticoresearch/manticore:latest |
Container image. Pin a tag in production. |
resources |
{ cpu = 500, memory = 512 } |
Task resources. Bump memory for large indexes. |
Connect with any MySQL client (mysql -h <node-ip> -P 9306) or the JSON API on 9308. The EXTRA=1 env
enables the auto-schema/buddy helpers for a smooth quick start. Ports are unauthenticated — keep them on
an internal network. Pin the job to the node holding the volume with constraints.