quay up
Live on testnet
One command applies quay.json: functions, collection rules, products, the members setting and cron jobs, then it deploys the site folder with its routes and promotes it. It never arms cron. --dry-run prints the plan and changes nothing. The Board was deployed with it.
Commands
quay up --dry-run quay up -m "harbour board"
Versioned with a release, and not
A release seals files, routes and templates, so quay rollback swaps those three. Docs, collection rules, products, members, function code and secrets, relay settings and cron jobs are live state, and a rollback leaves them alone.
Every flag is in the command reference, generated from quay up --help.