From 862e37a5054cddbc8e1af5eacb7f45a40474e6f8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jesu=CC=81s=20Pe=CC=81rez?= Date: Fri, 17 Jul 2026 06:37:52 +0100 Subject: [PATCH] chore: fix with --all --- site/update-content.sh | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/site/update-content.sh b/site/update-content.sh index 259c2ae..22091c5 100755 --- a/site/update-content.sh +++ b/site/update-content.sh @@ -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 # widen the changeset: what the pod lacks since +# ./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 #