Changes in scripts/klonkt-refresh-updater.sh [12bed59:5861849] in Klonkt

File:

• scripts/klonkt-refresh-updater.sh (modified) (2 diffs)

scripts/klonkt-refresh-updater.sh

@@ -30 +30 @@
 D="${KLONKT_DIR}"
 B=\$(runuser -u ${KLONKT_USER} -- git -C "\$D" rev-parse HEAD 2>/dev/null || true)
-runuser -u ${KLONKT_USER} -- git -C "\$D" fetch --depth 1 origin ${BRANCH}
+# Deepen a shallow checkout ONCE. \`fetch --depth 1\` keeps only the newest commit
+# and \`checkout -f\` throws away the tree that was there, so after an update the
+# previous version existed nowhere on the machine: a bad release could not be
+# undone without the network, and only if you knew which commit to ask for.
+# One deepening buys back the history; every later fetch keeps it.
+if [ "\$(runuser -u ${KLONKT_USER} -- git -C "\$D" rev-parse --is-shallow-repository 2>/dev/null)" = "true" ]; then
+  echo "deepening the checkout once so updates can be rolled back..."
+  runuser -u ${KLONKT_USER} -- git -C "\$D" fetch --unshallow origin ${BRANCH} || true
+fi
+runuser -u ${KLONKT_USER} -- git -C "\$D" fetch origin ${BRANCH}
 runuser -u ${KLONKT_USER} -- git -C "\$D" checkout -qf -B ${BRANCH} FETCH_HEAD
 A=\$(runuser -u ${KLONKT_USER} -- git -C "\$D" rev-parse HEAD)
@@ -55 +64 @@
   echo "Klonkt updated (\$A) + restarted \$N instance(s)."
 fi
+# History alone is not a rollback; at three in the morning you also need the
+# command. Print it while the previous commit is still known.
+if [ -n "\$B" ]; then
+  echo
+  echo "Previous version: \$B"
+  echo "To go back:"
+  echo "  runuser -u ${KLONKT_USER} -- git -C \$D checkout -qf -B ${BRANCH} \$B"
+  echo "  then restart the instances (systemctl restart 'klonkt@*')"
+fi
 EOF
 chmod +x /usr/local/bin/klonkt-update
 echo "klonkt-update rewritten: branch ${BRANCH}, code ${KLONKT_DIR}, instances under ${DATA_ROOT}"
 
-# On a split install the old single unit must not be startable at all.
-# `disable` is not enough (restart starts a disabled unit anyway) and `mask`
-# refuses while the real file sits in /etc/systemd/system, the highest-priority
-# directory. Moving the file aside is what actually works: systemd stops
-# knowing the unit, so any restart fails loudly instead of quietly starting a
-# second process that writes an empty database into the checkout.
+# On a split install the old single unit must not be startable. `disable` alone
+# does not stop `systemctl restart klonkt` from starting it, and a resurrected
+# klonkt.service has no .env (it moved with the data): it falls back to the
+# defaults and writes a fresh empty database into the checkout.
 SPLIT=0
 for d in "${DATA_ROOT}"/*/; do [ -f "$d/.env" ] && SPLIT=1 && break; done
-if [ "$SPLIT" = 1 ] && [ -f /etc/systemd/system/klonkt.service ]; then
-  systemctl stop klonkt.service 2>/dev/null || true
-  systemctl disable klonkt.service 2>/dev/null || true
-  RETIRED="/etc/systemd/system/klonkt.service.retired-$(date +%Y%m%d%H%M%S)"
-  if mv /etc/systemd/system/klonkt.service "$RETIRED"; then
-    systemctl daemon-reload
-    echo "retired klonkt.service → $RETIRED (move it back + daemon-reload to roll back)"
-  else
-    echo "WARNING: could not move /etc/systemd/system/klonkt.service aside."
-    echo "         Until you do, any 'systemctl restart klonkt' starts a second"
-    echo "         process that writes an empty database into ${KLONKT_DIR}."
+if [ "$SPLIT" = 1 ] && systemctl list-unit-files klonkt.service >/dev/null 2>&1; then
+  if ! systemctl is-enabled klonkt.service 2>/dev/null | grep -q masked; then
+    systemctl stop klonkt.service 2>/dev/null || true
+    systemctl disable klonkt.service 2>/dev/null || true
+    systemctl mask klonkt.service
+    echo "retired klonkt.service: stopped, disabled and masked (unmask to roll back)"
   fi
 fi