josh/Vetting
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

deploy: show speed + ETA in bundle-download progress meter
CI / Lint + build + test (push) Successful in 1m24s
Details
Release / release (push) Successful in 5m30s
Details

Browse Source 
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.
This commit is contained in:
Josh Wright
2026-04-18 15:04:26 -04:00
parent c45349f62c
commit 956120b80e
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/proxmox-install.sh
+6 -5
View File
@@ -39,11 +39,12 @@ tmp="$(mktemp -d)"
trap 'rm -rf "${tmp}"' EXIT trap 'rm -rf "${tmp}"' EXIT
echo "==> fetching bundle (${VETTING_VERSION}) from ${BUNDLE_URL}" echo "==> fetching bundle (${VETTING_VERSION}) from ${BUNDLE_URL}"
# --progress-bar (not -s) so the operator sees a live indicator — # Default curl meter (no -s, no --progress-bar) shows transfer rate
# bundles are ~30 MB and the registry can be slow on a cold run, and # and ETA, which matters now that bundles are ~300 MB — the live
# a silent 5 s has tricked us into Ctrl-C'ing mid-download before. # image ships the full firmware+rootfs, so a bare percentage bar
# -f keeps fail-on-HTTP-error; -L still follows redirects. # with no speed/ETA makes slow links look like hangs.
curl -fL --progress-bar "${BUNDLE_URL}" -o "${tmp}/vetting-bundle.tar.gz" # -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)" bundle_size="$(du -h "${tmp}/vetting-bundle.tar.gz" | cut -f1)"
echo "==> extracting (${bundle_size})" echo "==> extracting (${bundle_size})"