The zip2cloud application is a shell script that manages backup dumps, compresses them into zip files, compares them with existing backups in remote storage, and uploads any new or updated backups to the remote storage.

The script uses the following environment variables:

The script performs the following steps:

1. Cleanup: Removes old zip files and backup dumps based on the retention policies set in the environment variables.
2. Zip: Creates .7z archives of dump dirs (formatted as YYYY-MM-DD) in the $DUMP_BASE.
3. Checksum: Retrieves a list of remote backups and downloads the MD5 checksums for each remote backup into a temporary directory. It then compares the checksums of local zip files against the remote MD5 checksums, adding any files that don't match to an upload list.
4. Create Upload List: Verifies and updates the list of files to upload. For each file in the upload list, it compares the local and remote MD5 checksums. If there's a mismatch, it increments the filename and adds it to the final upload list. This incrementing process continues until it finds a filename that doesn't conflict with existing files in the remote storage.
5. Upload: Uploads the files in the final upload list to the remote storage using the rclone command.

The Dockerfile for this application is based on the alpine:latest image and includes the necessary binaries and files for the zip2cloud script. The Dockerfile uses a multi-stage build process to keep the final image size small.

The application uses GitHub Actions for continuous integration. The workflows are defined in the .github/workflows/ directory and include steps for building, tagging, and pushing Docker images, as well as scanning for vulnerabilities with Trivy.

This is a simple cron container for backing up databases such as ArangoDB, compressing the backups and then synchronizing a remote S3 bucket against a local archive of the compressed backups

1. [OPTIONAL] Perform a database dump based on environment variables provided, and place it in /dump/
2. Use 7zip to compress and encrypt the contents of the /dump/ directory and put it in into /zip/
   • The resulting zip will have have "dump/" as the relative root directory
3. Prune any files in /zip/ that are older than 30 days
4. Use rclone with an AWS S3 compatible provider to synchronize /zip/ against a remote S3 bucket and directory. Currently configured for Google Cloud Storage in file rclone.conf

This container requires the following secrets to be in /var/run/secrets:

• encryption_key - Encryption key used by 7zip for encryption of compressed files
• gcp_backup_creds - Google service credentials JSON secret for use with rclone (see rclone.conf file for service_account_file directive)

The following environment variables need to be passed into the runtime environment

• BUCKET - The name of the bucket to be used as the destinatio for copying the backups
• BUCKETPATH - Path with the bucket to deposit the zipped db files

The following volumes need to be mounted into the running container:

• /dump/ - Directory either containing existing DB dumps or which will be the destination for a DB dump.
• /zip/ - Directory for writing the compressed/encrypted DB dumps before copying to the S3 remote