Releases: dharmeshmp/rclone-copy-cron
🚀 Added Immediate Backup Feature
We are excited to introduce the Immediate Backup feature to the rclone-copy-cron
Docker image! 🎉
With this update, you can now run a backup immediately if the BACKUP_CRON
environment variable is not set. This provides more flexibility for use cases that require on-demand backups without the need for scheduling.
What's New?
-
Immediate Backup Mode:
- If
BACKUP_CRON
is not set, the container will:- Start the backup process immediately.
- Copy files from the source to the destination using Rclone.
- Exit after the backup completes.
- If
-
Improved Logging:
- Clear logs for immediate backup runs, including start and completion status.
How to Use?
To run an immediate backup, simply omit the BACKUP_CRON
environment variable in your Docker command:
docker run --rm \
-e RCLONE_SOURCE=source:my-source-bucket \
-e RCLONE_DESTINATION=backup:my-destination-bucket \
-e RCLONE_OPTIONS="--progress --checksum" \
dharmeshmp/rclone-copy-cron
This feature is perfect for one-time backup scenarios or testing your backup setup before scheduling.
Enhancements:
- Dual-Mode Support: Use scheduled backups (
BACKUP_CRON
) or immediate backups without changing the container image. - Simplified usage for non-recurring backup needs.
We hope this new feature makes your backup management even more seamless and efficient. 🚀
Feel free to share your feedback or suggestions!
Added Support for Configurable Time Zones
Release Highlights:
This release introduces support for specifying time zones in the container, allowing cron jobs to execute in the desired timezone instead of defaulting to UTC. The feature enhances scheduling flexibility and better accommodates users in different geographical regions.
New Features
- Time Zone Configuration:
Added theTIME_ZONE
environment variable to set the desired timezone for cron jobs. For example:By default, the timezone is set to-e TIME_ZONE="Asia/Kolkata"
UTC
.
Bug Fixes
- Improved cron job setup to ensure environment variables are correctly loaded and utilized.
- Enhanced logging mechanism for better real-time log visibility.
Usage Example
Run a container with a specific timezone:
docker run -d \
-e RCLONE_SOURCE=source:my-source-bucket \
-e RCLONE_DESTINATION=backup:my-destination-bucket \
-e BACKUP_CRON="0 2 * * *" \
-e TIME_ZONE="America/New_York" \
rclone-copy-cron
Thank you for using rclone-copy-cron! We look forward to your feedback and contributions.
Initial Release of rclone-copy-cron
We are excited to introduce the rclone-copy-cron, a Docker-based solution for scheduled file copy operations using Rclone. This first release brings the following features:
🚀 Features
- Flexible Scheduling: Schedule file copy operations using
BACKUP_CRON
environment variable with cron expressions. - Cloud Storage Support: Easily integrate with multiple cloud storage providers supported by Rclone, such as AWS S3, DigitalOcean Spaces, Google Drive, and more.
- Customizable Options: Configure Rclone commands with additional options like
--progress
,--fast-list
, and more. - Logging: View real-time logs in Docker terminal and access detailed logs at
/var/log/copy.log
. - Lightweight and Portable: Built on the lightweight
rclone/rclone
image with minimal dependencies.
📦 How to Use
- Docker Run: Run the container with required environment variables to start scheduled copy operations.
- Docker Compose: Simplify deployment with a
docker-compose.yml
file for managing services.
🌟 Get Started
Check the [README](link-to-readme) for detailed usage instructions, examples, and supported environment variables.
🛠️ What's Next?
Future updates may include:
- Support for advanced Rclone configurations.
- Enhanced logging and monitoring capabilities.
- Integration with more storage services.
We look forward to your feedback and contributions!