Yann Autissier
32e2624245
The skill documents how to use myos: what to check before touching a host stack, how a reference resolves, what the three kinds of stack mean, and where each failure comes from. Every command it shows was run against the fixtures before being written down, which is how exec, run and scale turned out to be missing. AGENTS.md covers the other side: how to change myos without breaking the deployments that already run it.
14 lines
532 B
Bash
14 lines
532 B
Bash
#shellcheck shell=sh
|
|
# shellcheck source=lib/cmd/_compose.sh
|
|
# myos scale <stack> SERVICE=<name> NUM=<n> run n containers of a service
|
|
. "$MYOS_ROOT/lib/cmd/_compose.sh"
|
|
|
|
myos_cmd_scale() {
|
|
_ref=$(printf '%s' "$MYOS_STACKS" | head -1)
|
|
[ -n "$_ref" ] || myos_die "$MYOS_E_USAGE" "usage: myos scale <stack> SERVICE=name NUM=n"
|
|
_service=${SERVICE:-$(myos_stack_name "$_ref")}
|
|
[ -n "${NUM:-}" ] || myos_die "$MYOS_E_USAGE" "myos scale needs NUM=<n>"
|
|
MYOS_ARGS="--scale $_service=$NUM ${MYOS_ARGS:-}"
|
|
myos_cmd_compose up
|
|
}
|