bur4kbey / docker-auto-backup Goto Github PK

Goal

The objective here is to establish a system for direct backups from containers as specified in the configuration file, while also enabling the execution of pre and post scripts within each container.

Implementation

• Read and parse the configuration file.
• Execute pre_build_script and post_build_script scripts for each container, if specified.
• Retrieve the specified files from each container to the backup folder.
• Document the changes to the README.md

Why?

Consider a scenario where you have a running PostgreSQL container and you require periodic backups. Attempting to directly volume the path to the backup container might inadvertently include unnecessary binaries, bloating the backup file size. With this feature, you can utilize pre-build scripts to generate a backup from your PostgreSQL instance and then backup the generated SQL file, ensuring only essential data is included.

Example Configuration File

containers:
  - name: service-1
    files:
      - /data/.:/backup/service-1/data

  - name: service-2
    files:
      - /data/.:/backup/service-2/data
    pre_build_script: |
      touch /root/logs
      echo "pre-build script ran" >> /root/logs
    post_build_script: |
      echo "post-build script ran" >> /root/logs

Goal

The goal of this issue is to implement push notifications using ntfy whenever the backup system encounters issues uploading the generated backup to the desired cloud providers.

Specifics:

• Send a push notification if the backup upload fails.
• Send a push notification if the backup upload succeeds.

Implementation

• Send HTTP/HTTPS requests to ntfy servers.
• Support custom CA files for ntfy servers using self-signed certificates.