drestic, branch v1.3.1CLI for setting up & automating restic + mega backupshttp://git.samsci.com/cgit.cgi/drestic/atom?h=v1.3.12025-10-23T23:18:05ZBump version to 1.3.12025-10-23T23:18:05ZSam Scholten2025-10-23T23:18:05Zurn:sha1:0af934099f5b9af34b9fad53ce1100c723db8bb9Add timer updates to update.sh and create upgrade make target2025-10-23T23:17:13ZSam Scholten2025-10-23T23:17:13Zurn:sha1:025e2281697ec4a5655c389f012087835c165302
- Modified update.sh to also copy timer files (restic-backup.timer and restic-check.timer)
- Added 'upgrade' make target that reminds users to git pull first
- Updated help text to clarify difference between 'update' and 'upgrade'
Bump version to 1.3.02025-10-23T23:12:36ZSam Scholten2025-10-23T23:12:36Zurn:sha1:bbeb5907d4518a606086cae0aff063d1aca2a009Stagger backup times to prevent conflicts2025-10-23T23:10:47ZSam Scholten2025-10-23T23:10:47Zurn:sha1:bc7e13c12febe0082abd48b719097ed119c3405d
- Set backup timer to run at 1 AM with 3-hour random delay (1-4 AM window)
- Add 1-hour random delay to weekly check timer
- This prevents multiple devices from backing up simultaneously
Remove unsupported --retry-lock flags for restic 0.14.0 compatibility2025-10-23T23:07:22ZSam Scholten2025-10-23T23:07:22Zurn:sha1:a59db227f0fb4e0a3521e2d9f90031645b8b5e1a
The --retry-lock flag was added in restic 0.17.0, but Debian 12 ships
with restic 0.14.0. Removing these flags ensures compatibility with
older restic versions while still maintaining functionality.
Fix systemd service path replacement in setup.sh2025-10-23T23:01:44ZSam Scholten2025-10-23T23:01:44Zurn:sha1:d8dec8bbb471dfca9fe0535edc0c2906c7f91740
The sed commands were using 'ExecStart=.*' which didn't match the exact
placeholder path '/path/to/be/replaced/restic_backup.sh'. Updated to use
the full path pattern for both backup and check services.
Fix make config to detect system scope configuration (second fix)2025-10-23T23:00:00ZSam Scholten2025-10-23T23:00:00Zurn:sha1:59af76dc28655316c5176c9262bf05f757dc9f56
Added sudo before checking for /root/.restic_env in the config target's elif condition.
The previous commit only fixed the validate-config target, not the config target.
Fix make config to detect system scope configuration2025-10-23T22:56:18ZSam Scholten2025-10-23T22:56:18Zurn:sha1:0f99db5d30bdaadf6cfd8f8e3405a6f35c2398aa
Add sudo before checking for /root/.restic_env in the config target.
Without sudo, the check runs as the regular user and can't see the
system scope environment file, causing make config to incorrectly
report 'No DRestic configuration found' when system scope is set up.
Add logo to readme2025-10-23T05:30:41ZSam Scholten2025-10-23T05:30:41Zurn:sha1:04f28e2e6496195e16afdfed26135180b8600993fix: Handle missing scripts gracefully in update.sh chmod2025-10-22T06:57:49ZSam Scholten2025-10-22T06:57:49Zurn:sha1:ebabbea04473cf4eebee57996c9cc210ad2fd203