Check against your doze

MinIO

Bring your ownNot signed by doze

S3-compatible object storage. doze runs your MinIO: the minio you installed, the minio/minio container, or an archive you pin.

doze add minio · port 9000

Not a module: doze runs your MinIO. There is no doze/minio in the registry. doze add minio 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 minio --as installed

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

doze.hcl

service "minio" {
  run  = "minio server $DATA --address $HOST:$PORT --console-address $HOST:$((PORT + 1))"
  port = 9000
}

Container

if minio isn't installed

$ doze add minio --as container

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

doze.hcl

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

Download

pinned by sha256

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

terminal: plain doze add, on a machine without minio

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

  use it from an app:  MINIO_ADDR = service.minio.address

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

What doze still gives it

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

What it doesn't

No signature. doze didn't build minio 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 minio is on the PATH, or whatever minio/minio points at today.
No declared databases or users. A module converges those from doze.hcl; a service is just a process.

Want S3 from the registry? doze AWS.

S3 with SQS, SNS, DynamoDB, Lambda and more behind one port, signed and pinned like every module, with buckets and queues declared in doze.hcl.

$ doze add aws

The aws 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
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
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