Backups push automatically; the token is only for restore

Matches the master's tokenless-push change: pushBackup no longer waits
for master_backup_token — every instance with a uuid backs up on its
own, and the 5-minute tick force-pushes so a poisoned master copy
self-heals. The token now only gates pulling a backup back (restore),
so setup-linux.sh asks for it only when restoring and the Settings
help text says so.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Brandon Li
2026-09-22 14:08:03 -05:00
co-authored by Claude Fable 5
parent 8154f25bb9
commit ba8bd50da0
4 changed files with 27 additions and 22 deletions
+5 -4
View File
@@ -86,10 +86,11 @@ read -r -p " Master dashboard URL [$DEFAULT_MASTER]: " MASTER_URL
MASTER_URL="${MASTER_URL:-$DEFAULT_MASTER}"
read -r -p " Instance name [$(hostname)]: " INSTANCE
INSTANCE="${INSTANCE:-$(hostname)}"
read -r -p " Backup token (blank = no master backups): " BACKUP_TOKEN
RESTORE_FROM=""
if [ -n "$BACKUP_TOKEN" ]; then
read -r -p " Restore a dead instance? Its uuid (blank = fresh install): " RESTORE_FROM
# Backups push automatically; the token is only needed to pull one back.
read -r -p " Restore a dead instance? Its uuid (blank = fresh install): " RESTORE_FROM
BACKUP_TOKEN=""
if [ -n "$RESTORE_FROM" ]; then
read -r -p " Backup token (the master's INSTANCE_BACKUP_TOKEN): " BACKUP_TOKEN
fi
echo
info "installing to: $TARGET"