manage.sh: standardize cloud commands to hyphen syntax (cloud-start vs cloud:start) #1

New issue

Closed

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

pyr0ball commented

2026-05-05 20:36:34 -07:00

Owner

Problem

Pagepiper uses cloud:start / cloud:stop / cloud:restart / cloud:status / cloud:logs / cloud:build (colon separator), while Kiwi and Snipe use cloud-start etc. (hyphen separator). This inconsistency makes muscle memory painful when switching between products.

Desired

Rename all cloud:* subcommands to cloud-* to match the majority convention:

./manage.sh cloud-start
./manage.sh cloud-stop
./manage.sh cloud-restart
./manage.sh cloud-status
./manage.sh cloud-logs
./manage.sh cloud-build

Keep old colon-form as an alias during a transition if needed.

Context

Audit of manage.sh parity across all CF products (2026-05-05). Kiwi and Snipe are the reference for this convention.

## Problem Pagepiper uses `cloud:start` / `cloud:stop` / `cloud:restart` / `cloud:status` / `cloud:logs` / `cloud:build` (colon separator), while Kiwi and Snipe use `cloud-start` etc. (hyphen separator). This inconsistency makes muscle memory painful when switching between products. ## Desired Rename all `cloud:*` subcommands to `cloud-*` to match the majority convention: ``` ./manage.sh cloud-start ./manage.sh cloud-stop ./manage.sh cloud-restart ./manage.sh cloud-status ./manage.sh cloud-logs ./manage.sh cloud-build ``` Keep old colon-form as an alias during a transition if needed. ## Context Audit of manage.sh parity across all CF products (2026-05-05). Kiwi and Snipe are the reference for this convention.