CLI
Up
Start the services of your build file and keep them running.
Services normally start and stop automatically based on the needs of the tasks
you run. The up command starts them directly, which is useful to keep shared
services such as a database running across several task runs during development.
hammerkit upThis starts every service in the build file (or the ones matching the
--filter/--exclude labels) and waits until you stop it. Use --daemon to
start the services in the background and return immediately.
hammerkit up --daemonStop services started this way with hammerkit down.
Pass --env <name> to start the services in a configured environment, for
example a Kubernetes cluster declared under environments:. See
running on Kubernetes.
Options
Options:
-f, --filter <labels...> filter task and services with labels
-e, --exclude <labels...> exclude task and services with labels
-c, --concurrency <number> parallel worker count (default: 4)
-w, --watch watch tasks (default: false)
-d, --daemon run services in background (default: false)
--env <name> environment
-l, --log <mode> log mode (choices: "interactive", "live", "grouped")
--cache <method> caching method to compare (choices: "checksum", "modify-date", "none")
--cache-read-only restore from cache backends but never push to them (or set HAMMERKIT_CACHE_READ_ONLY=1)
--timeout <duration> fail tasks without their own timeout after this long (e.g. 10m)
-h, --help display help for command