manage.sh: expose cloud-start / cloud-restart / demo-restart commands #114

New issue

Closed

opened 2026-05-05 20:45:05 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-05-05 20:45:05 -07:00

Owner

Problem

Pagepiper, Kiwi, and Snipe all expose cloud-start / cloud-restart / cloud-status / cloud-logs / cloud-build directly from manage.sh. Peregrine operators must know that cloud and demo stacks live in compose.cloud.yml and compose.demo.yml and invoke them via make or direct docker compose — these are not discoverable from ./manage.sh help.

Desired

./manage.sh cloud-start    # docker compose -f compose.cloud.yml -p peregrine-cloud up -d --build
./manage.sh cloud-stop
./manage.sh cloud-restart
./manage.sh cloud-status
./manage.sh cloud-logs
./manage.sh cloud-build
./manage.sh demo-start     # same pattern for compose.demo.yml / peregrine-demo
./manage.sh demo-stop
./manage.sh demo-restart
./manage.sh demo-status
./manage.sh demo-logs
./manage.sh demo-build

Note: Peregrine demo uses --no-cache to force cf-core reinstall from git (see 2026-05-05 deployment notes).

Context

Parity audit across all CF manage.sh files (2026-05-05). Discovered during cf-core v0.20.0 rollout when cloud/demo containers were initially missed because the rebuild path wasn't obvious.

## Problem Pagepiper, Kiwi, and Snipe all expose `cloud-start` / `cloud-restart` / `cloud-status` / `cloud-logs` / `cloud-build` directly from `manage.sh`. Peregrine operators must know that cloud and demo stacks live in `compose.cloud.yml` and `compose.demo.yml` and invoke them via `make` or direct `docker compose` — these are not discoverable from `./manage.sh help`. ## Desired ```bash ./manage.sh cloud-start # docker compose -f compose.cloud.yml -p peregrine-cloud up -d --build ./manage.sh cloud-stop ./manage.sh cloud-restart ./manage.sh cloud-status ./manage.sh cloud-logs ./manage.sh cloud-build ./manage.sh demo-start # same pattern for compose.demo.yml / peregrine-demo ./manage.sh demo-stop ./manage.sh demo-restart ./manage.sh demo-status ./manage.sh demo-logs ./manage.sh demo-build ``` Note: Peregrine demo uses `--no-cache` to force cf-core reinstall from git (see 2026-05-05 deployment notes). ## Context Parity audit across all CF manage.sh files (2026-05-05). Discovered during cf-core v0.20.0 rollout when cloud/demo containers were initially missed because the rebuild path wasn't obvious.