chore: fix with --all
This commit is contained in:
parent
222d18e3cb
commit
862e37a505
1 changed files with 10 additions and 1 deletions
|
|
@ -4,7 +4,16 @@
|
|||
# reload_classes): hot → no restart · restart → snapshot + rolling restart ·
|
||||
# rebuild → refused (that one needs a new image, not content).
|
||||
#
|
||||
# ./update-content.sh # classify + publish
|
||||
# ./update-content.sh # classify + publish what changed since HEAD~1
|
||||
# ./update-content.sh --all # SEND EVERYTHING — the whole deliverable tree,
|
||||
# # for when the pod's state is not trusted (a bad
|
||||
# # commit, a deploy that never landed). The action
|
||||
# # still follows what CHANGED, not what is sent.
|
||||
# ./update-content.sh --since <sha> # widen the changeset: what the pod lacks since <sha>
|
||||
# ./update-content.sh --all --restart # SEND EVERYTHING AND RESTART. For the first delivery
|
||||
# # of a startup-read file (migrations, config) that
|
||||
# # git has carried for weeks and so reads as
|
||||
# # "unchanged" while the pod has never had it.
|
||||
# ./update-content.sh --dry-run # say what it would do, touch nothing
|
||||
# ./update-content.sh --namespace x # any content.nu flag passes through
|
||||
#
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue