Check against your doze

ClickHouse

Bring your ownNot signed by doze

A column-store analytics database. doze runs your ClickHouse: the clickhouse/clickhouse-server container, or an archive you pin.

doze add clickhouse · port 8123

Not a module: doze runs your ClickHouse. There is no doze/clickhouse in the registry. doze add clickhouse writes a service block, takes the first way that works on your machine, and names the other two.

Two ways to run it, and the block each writes

Container

first choice

$ doze add clickhouse --as container

A container is just a command that stays in the foreground. Needs Docker or a compatible runtime. doze knows no run line for an installed clickhouse, so this is the block it writes.

doze.hcl

service "clickhouse" {
  # a container: a container is just a command, and `run` stays in the foreground
  run  = "docker run --rm -p $HOST:$PORT:8123 clickhouse/clickhouse-server"
  port = 8123
}

Download

pinned by sha256

$ doze add clickhouse --as download

You fill in the archive URL and the real run line; doze fetches it once and pins its checksum in doze.lock.

doze.hcl: fill in download and run

service "clickhouse" {
  # fetched once, pinned in doze.lock by its checksum, and run from the archive
  download = "https://example.com/clickhouse-darwin-arm64.tar.gz" # fill this in
  run      = "./clickhouse --port $PORT"
  port     = 8123
}

terminal: plain doze add, on a machine without clickhouse

$ doze add clickhouse
→ clickhouse is not a doze module — adding it as a service
  clickhouse is not installed — the block runs it as a container
  other ways: --as installed · --as container · --as download

  use it from an app:  CLICKHOUSE_ADDR = service.clickhouse.address

$HOST, $PORT and $DATA are filled in at run time.

What doze still gives it

A name: clickhouse.<stack>.doze, and your own domain over https if you set one.
A port, held by doze while ClickHouse is asleep.
Sleep and wake: it wakes when a client connects and sleeps when nothing has for a while. Data stays in $DATA.
Logs in doze logs clickhouse and in the app, next to everything else.

What it doesn't

No signature. doze didn't build the image, so it doesn't sign it. A download is pinned by sha256 in doze.lock: a changed file is refused, but nobody vouched for the first one.
No pinned version for the container. You get whatever clickhouse/clickhouse-server points at today.
No declared databases or users. A module converges those from doze.hcl; a service is just a process.

The other tools doze add knows

Each gets the same three ways where it can. rabbitmq, opensearch and clickhouse have no known run line, so installed falls back to the container.

Name	What it is	Runs from	Port
mongo	The document database	mongod · mongo:7	27017
mailpit	Catches outgoing email; web inbox on the next port	mailpit · axllent/mailpit	1025
minio	S3-compatible object storage (doze AWS has S3 too)	minio · minio/minio	9000
nats	Messaging and streams	nats-server · nats	4222
meilisearch	Typo-tolerant search engine	meilisearch · getmeili/meilisearch	7700
memcached	The classic in-memory cache	memcached · memcached	11211
rabbitmq	AMQP message broker	container rabbitmq:3	5672
opensearch	Search and log analytics	container opensearchproject/opensearch	9200

Anything else: doze add <name> writes a download block to fill in. What that looks like