Deploy Manticore Search
Private Manticore Search database with persistent storage and HTTP/SQL interfaces.
Manticore Search
Just deployed
/var/lib/manticore
Deploy Manticore Search on Railway
Manticore Search is an open-source search database with full-text search, SQL, and a JSON/HTTP API. This template runs the official manticoresearch/manticore:29.9.0 image, the latest stable release verified on November 17, 2026.
Included configuration
- Persistent volume at
/var/lib/manticore, the official image's actual data directory. Mounting only/datawould not persist the default database files. - Private HTTP API on 9308, MySQL-compatible SQL on 9306, and binary protocol on 9312 as provided by the upstream image.
- No public domain or TCP proxy by default. Manticore interfaces must not be exposed to the internet without an authentication and access-control layer.
- Railway startup probe at
/sql?mode=raw&query=SELECT%201on port 9308, with a 300-second timeout and bounded failure retries. This checks the HTTP/SQL path, not index correctness or backup freshness. - The official entrypoint is retained so it can initialize the data directory, handle ownership, and drop to the Manticore user. The current image already bundles Manticore Extra and Buddy; the obsolete
EXTRA=1template toggle is removed.
Connect from your application
Deploy the application in the same Railway project and environment. Reference the generated MANTICORE_HTTP_URL variable from the Manticore service, or use http://<private-service-domain>:9308. Railway private addresses are not reachable directly from your laptop or the public internet.
For a MySQL-compatible client, connect to the service's private domain on port 9306. This is the Manticore SQL dialect, not a general-purpose MySQL server. The connection metadata does not create an authentication boundary; keep the service on the private network.
Example from another service in the same environment:
curl --fail-with-body "$MANTICORE_HTTP_URL/sql?mode=raw&query=SELECT%201"
Create a small test table, insert a document, and search for it before connecting production traffic. Restart the service and confirm that the table and document survive.
If you need remote administration, use a deliberately secured access path. Do not publish raw port 9308 or 9306 simply to make local testing convenient.
Production considerations
Keep one replica for the local store. Size RAM and disk for indexes and query load; running out of memory can cause restart loops. Configure scheduled volume backups, retention, off-platform recovery where appropriate, and periodic restore tests. A successful deployment probe does not prove data durability.
Back up before upgrading, review release notes and index-format changes, and update image tags deliberately. Do not replace the official start command unless you also take responsibility for configuration and initialization.
Updating this template does not migrate an existing deployment. If the previous installation mounted /data, inspect where the database actually stored its files and export or back them up before replacing the container; changing the mount path alone cannot recover an ephemeral database.
References
Template Content
Manticore Search
manticoresearch/manticore:29.9.0