Self-host Sonic with Levelrail

Fast, lightweight schema less search index server that stores identifiers instead of documents. The install form carries config.cfg as an editable file and a generated channel password.

How to self-host Sonic

  1. Pull the images

    One image is pulled on your server.

    Show images
    • valeriansaliou/sonic:v1.10.2
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 1491.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Connect a Sonic client library to port 1491 with the generated channel password shown in the deployment variables.

Sonic requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
1491
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MPL-2.0, copyleft license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Sonic. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Sonic docs page.

Deploy Sonic your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Sonic from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain sonic=app.example.com.

levelrail-cli templates install sonic --name my-sonic

Deploy Sonic with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/sonic/install \
  -d '{
    "name": "my-sonic"
  }'

Sonic configuration

Sonic services

ServiceImagePortsVolumes
sonic valeriansaliou/sonic:v1.10.2 1491 store -> /var/lib/sonic/store

Sonic environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
1491
Volumes
1 named mount: store -> /var/lib/sonic/store

Sonic FAQ

How much memory does Sonic need?

The catalog lists about 128 MiB of memory for Sonic.

Does Sonic run on arm64?

For Sonic, arm64 support is not confirmed; amd64 is unknown.

What licence is Sonic under?

Sonic is licensed under MPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does Sonic need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Sonic use?

Sonic listens on port 1491 inside the stack.

Where does Sonic keep its data?

In a named volume: store mounted at /var/lib/sonic/store.

Can I deploy Sonic on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Sonic, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image valeriansaliou/sonic:v1.10.2 is what you deploy there.

levelrail-cli templates install sonic --name my-sonic