RegistryCheck against your doze
Check against your doze
Checking against doze
Bring your own
Not everything is a module. For 9 tools doze knows how to run what you already have: the binary you installed, a container, or an archive you pin.
Not modules: doze runs your tools. None of these is in the registry.
doze add <name> writes a service block, takes the first way that works on your machine, and names the others: --as installed, --as container, --as download.The 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 | Port |
|---|---|---|
| mongo | The document database | 27017 |
| mailpit | Catches outgoing email; web inbox on the next port | 1025 |
| minio | S3-compatible object storage (doze AWS has S3 too) | 9000 |
| nats | Messaging and streams | 4222 |
| meilisearch | Typo-tolerant search engine | 7700 |
| memcached | The classic in-memory cache | 11211 |
| rabbitmq | AMQP message broker | 5672 |
| opensearch | Search and log analytics | 9200 |
| clickhouse | Column-store analytics database | 8123 |
Anything else: doze add <name> writes a download block to fill in. What that looks like
What doze still gives them
- A name:
<name>.<stack>.doze, and your own domain over https if you set one. - A port, held by doze while the tool 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 <name>and in the app, next to everything else.
What they don't
- No signature. doze didn't build the binary 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 is on the PATH, or whatever the image tag points at today.
- No declared databases or users. A module converges those from doze.hcl; a service is just a process.