From 956120b80eaed42617918601830688052331cbf3 Mon Sep 17 00:00:00 2001
From: josh <josh@thewrightserver.net>
Date: Sat, 18 Apr 2026 15:04:26 -0400
Subject: [PATCH] deploy: show speed + ETA in bundle-download progress meter

Drop --progress-bar (curl's minimal hash meter) in favor of the default
progress output, which includes transfer rate and time remaining.
Bundles grew from ~30 MB to ~300 MB with the full-rootfs initrd, and
a percentage-only bar with no speed hint makes a slow registry look
indistinguishable from a hang.
---
 deploy/proxmox-install.sh | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/deploy/proxmox-install.sh b/deploy/proxmox-install.sh
index 77634df..5e2681c 100644
--- a/deploy/proxmox-install.sh
+++ b/deploy/proxmox-install.sh
@@ -39,11 +39,12 @@ tmp="$(mktemp -d)"
 trap 'rm -rf "${tmp}"' EXIT
 
 echo "==> fetching bundle (${VETTING_VERSION}) from ${BUNDLE_URL}"
-# --progress-bar (not -s) so the operator sees a live indicator —
-# bundles are ~30 MB and the registry can be slow on a cold run, and
-# a silent 5 s has tricked us into Ctrl-C'ing mid-download before.
-# -f keeps fail-on-HTTP-error; -L still follows redirects.
-curl -fL --progress-bar "${BUNDLE_URL}" -o "${tmp}/vetting-bundle.tar.gz"
+# Default curl meter (no -s, no --progress-bar) shows transfer rate
+# and ETA, which matters now that bundles are ~300 MB — the live
+# image ships the full firmware+rootfs, so a bare percentage bar
+# with no speed/ETA makes slow links look like hangs.
+# -f fails on HTTP errors; -L follows redirects.
+curl -fL "${BUNDLE_URL}" -o "${tmp}/vetting-bundle.tar.gz"
 
 bundle_size="$(du -h "${tmp}/vetting-bundle.tar.gz" | cut -f1)"
 echo "==> extracting (${bundle_size})"