Reference
Coming from Dokku
Same commands, same git push. What changes is where your apps run and how many servers they can use.
Jokku keeps Dokku's command names, argument order and output. apps:create, config:set, ps:scale, domains:add, ssh-keys:add and git push all work the way you expect, and tools that speak Dokku's protocol, like dokku/github-action, work unchanged.
What's different#
Choosing a builder#
This is the one area that departs from Dokku. Rather than builder:set selected and per-builder settings, Jokku has one command per way of building:
builder:set still handles build-dir and procfile; the Procfile path moved there from ps:set procfile-path.
Things to know#
- Volumes are disks, not directories. A process with a volume runs one instance, and its deploys stop the old instance first. See Volumes.
- HTTPS is off for new apps, as in Dokku. Turn it on with
letsencrypt:enable. resource:reserveisn't needed. In a microVM, the memory limit is the reservation.- Apps listen on
$PORT.ports:*mapping is planned. - Not planned:
nginx:*(Caddy replaces nginx),plugin:*andps:inspect(useps:report).
See the command reference for every command and its status.