Check against your doze

Memcached

Bring your ownNot signed by doze

The classic in-memory cache. doze runs your Memcached: the memcached you installed, the memcached container, or an archive you pin.

doze add memcached · port 11211

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

Three ways to run it, and the block each writes

Installed

first choice

$ doze add memcached --as installed

Runs the memcached on your PATH. If there is none: memcached is not on your PATH: install it, or use --as container or --as download

doze.hcl

service "memcached" {
  run  = "memcached -l $HOST -p $PORT"
  port = 11211
}

Container

if memcached isn't installed

$ doze add memcached --as container

A container is just a command that stays in the foreground. Needs Docker or a compatible runtime.

doze.hcl

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

Download

pinned by sha256

$ doze add memcached --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 "memcached" {
  # fetched once, pinned in doze.lock by its checksum, and run from the archive
  download = "https://example.com/memcached-darwin-arm64.tar.gz" # fill this in
  run      = "./memcached --port $PORT"
  port     = 11211
}

terminal: plain doze add, on a machine without memcached

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

  use it from an app:  MEMCACHED_ADDR = service.memcached.address

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

What doze still gives it

A name: memcached.<stack>.doze, and your own domain over https if you set one.
A port, held by doze while memcached 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 memcached and in the app, next to everything else.

What it doesn't

No signature. doze didn't build memcached or the image, so it doesn't sign them. 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 installed or container. You get whatever memcached is on the PATH, or whatever memcached points at today.
No declared databases or users. A module converges those from doze.hcl; a service is just a process.

Want a cache from the registry? Valkey.

Redis-compatible, signed and pinned like every module, with its memory limit and eviction policy declared in doze.hcl.

$ doze add valkey

The valkey module →

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
rabbitmq	AMQP message broker	container rabbitmq:3	5672
opensearch	Search and log analytics	container opensearchproject/opensearch	9200
clickhouse	Column-store analytics database	container clickhouse/clickhouse-server	8123

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