custom notification's not working in 4.1.19 or 4.1.21

[johntdyer]

Summary

I am seeing no reference to it being configured in the startup and also no logging of it trying to send after a test backup

Steps to reproduce

services:

  uptime-kuma-db-backup:
   # https://github.com/tiredofit/docker-db-backup?tab=readme-ov-file#custom-notifications
    container_name: uptime-kuma-db-backup
    image: tiredofit/db-backup

    volumes:
      - /mnt/observability/uptime_kuma/maria-db/backups:/backup
    environment:
      TIMEZONE: America/New_York

      CONTAINER_ENABLE_MONITORING: FALSE

      ENABLE_NOTIFICATIONS: "true"
      NOTIFICATION_TYPE: "custom"
      NOTIFICATION_CUSTOM_SCRIPT: /backup/scripts/healthcheck.sh

      DEBUG_MODE: TRUE

      USER_DBBACKUP: 3003
      GROUP_DBBACKUP: 3003

      BACKUP_JOB_CONCURRENCY: "1"     # Only run one job at a time
      DEFAULT_CHECKSUM: "NONE"        # Don't create checksums
      DEFAULT_COMPRESSION: "ZSTD"     # Compress all with ZSTD
      DEFAULT_BACKUP_INTERVAL: "1440"   # Backup every 1440 minutes
      DEFAULT_BACKUP_BEGIN:  "+1"      # Start backing up at midnight
      DEFAULT_CLEANUP_TIME: "8640"    # Cleanup backups after a week

      DB01_TYPE: "mariadb"
      DB01_HOST: "uptime-kuma-db"
      DB01_NAME: "uptime"
      DB01_USER: "uptime"
      DB01_PASS: "uptime"

      # DB01_BACKUP_INTERVAL: "30"        # (override) Backup every 30 minutes
      # DB01_BACKUP_BEGIN: "+1"           # (override) Backup starts immediately
      DB01_CLEANUP_TIME: "180"        # (override) Cleanup backups they are older than 180 minutes
      DB01_CHECKSUM: "SHA1"           # (override) Create a SHA1 checksum
      DB01_COMPRESSION: "GZ"          # (override) Compress with GZIP
    restart: always
    networks:
      - uptime-kuma-internal

What is the expected correct behavior?

I would expect to see some logging of it being setup, like #419

Relevant logs and/or screenshots

docker.txt

Environment

• Image version / tag: 4.1.21, 4.1.19
• Host OS: debian