auberge backup push

Push local backups to an offsite restic repository. Alias: auberge b p.

auberge backup push [OPTIONS]

The repository is initialized automatically on first push.

Tip

push is upload-only — it never applies the retention policy. backup sync is the retention-enforcing entrypoint (it runs prune after push); standalone pushes accumulate snapshots until the next sync or manual backup prune.

Options

Option	Description	Default
-H, --host HOST	Filter backups by host	Interactive (if multiple hosts)
-b, --backup-id ID	Specific backup timestamp	latest

Setup

Before first use, configure rclone and restic:

# 1. Install restic and rclone
brew install restic rclone   # or: sudo apt install restic rclone

# 2. Configure an rclone remote for your storage provider (follow interactive wizard)
rclone config   # create remote named e.g. "offsite" — any rclone-supported backend
rclone mkdir offsite:auberge-backup

# 3. Set auberge config
auberge config set restic_repository "rclone:offsite:auberge-backup"
auberge config set restic_password "your-encryption-passphrase"

Any restic-supported repository string works; rclone: remotes keep provider credentials in rclone’s own config, so no extra environment variables are needed.

Tip

restic_password is NOT your storage provider’s password — it is restic’s own encryption key. Store it in a password manager; losing it means losing access to all snapshots. Both values support ! command syntax: auberge config set restic_password '!pass show auberge/restic'.

Examples

auberge backup push
auberge backup push --host myserver
auberge backup push --host myserver --backup-id 2026-03-09_14-30-00