[PR #129] [MERGED] Added cron reference in README.md #186

Closed
opened 2026-02-27 08:14:48 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/lucascbeyeler/zmbackup/pull/129
Author: @enribar
Created: 2/15/2019
Status: Merged
Merged: 2/20/2020
Merged by: @lucascbeyeler

Base: 1.2-versionHead: patch-1


📝 Commits (1)

  • 7ad8675 Added cron reference in README.md

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

📝 README.md (+5 -0)

📄 Description

I noticed that backup are automatically scheduled by the installer, but it is not mentioned anywhere how they are scheduled and how to edit that schedule.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/lucascbeyeler/zmbackup/pull/129 **Author:** [@enribar](https://github.com/enribar) **Created:** 2/15/2019 **Status:** ✅ Merged **Merged:** 2/20/2020 **Merged by:** [@lucascbeyeler](https://github.com/lucascbeyeler) **Base:** `1.2-version` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`7ad8675`](https://github.com/lucascbeyeler/zmbackup/commit/7ad8675b8a91d8adfa8aa41f65538b750ac5ccc0) Added cron reference in README.md ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+5 -0) </details> ### 📄 Description I noticed that backup are automatically scheduled by the installer, but it is not mentioned anywhere how they are scheduled and how to edit that schedule. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-27 08:14:48 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/zmbackup#186
No description provided.