Minituff/nautical-backup v2.25.0

on GitHub

Custom Report File Names (REPORT_FILE_NAME)

You can now customize the prefix used in the report file's name. This is especially useful if you run multiple Nautical instances against the same destination folder — by default, every instance writes to the same Backup Report - YYYY-MM-DD.txt, so whichever instance runs last silently overwrites the others' report.

REPORT_FILE_NAME=server-1-backup

This produces a report file named server-1-backup - YYYY-MM-DD.txt. The date is always appended, so this only changes the prefix — it doesn't disable daily-dated report files.

If you're already running multiple instances with a custom LABEL_PREFIX, you can reuse that same value instead of typing it twice, using the {PREFIX} token (aliases: {label_prefix}, {LABEL_PREFIX}, {prefix}, {PREFIX} all work the same way):

services:
  nautical-inst1:
    environment:
      - LABEL_PREFIX=nautical-backup.inst1
      - REPORT_FILE_NAME={PREFIX}
  nautical-inst2:
    environment:
      - LABEL_PREFIX=nautical-backup.inst2
      - REPORT_FILE_NAME={PREFIX}

This produces nautical-backup.inst1 - YYYY-MM-DD.txt and nautical-backup.inst2 - YYYY-MM-DD.txt respectively, so each instance's report file is named after its own LABEL_PREFIX automatically.

REPORT_FILE_NAME is unset by default, so existing setups are unaffected — the report file name stays exactly Backup Report - YYYY-MM-DD.txt unless you opt in.

(Closes #740)

What's Changed

• feat: allow customization of report file name prefix with support for tokens by @Minituff in #742
• chore(deps): update github-actions (major) by @renovate[bot] in #706

Full Changelog: v2.24.0...v2.25.0