Renovate Bot
ea786500b5
Some checks are pending
Dev Version / Release (push) Waiting to run
Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `.forgejo/workflows/dev.yml` (github-actions) * `.forgejo/workflows/release.yml` (github-actions) * `go.mod` (gomod) * `vendor/github.com/urfave/cli/v2/mkdocs-requirements.txt` (pip_requirements) ### What to Expect With your current configuration, Renovate will create 6 Pull Requests: <details> <summary>chore(deps): update module github.com/aws/aws-sdk-go to v1.55.5</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-aws-aws-sdk-go-1.x` - Merge into: `main` - Upgrade [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) to `v1.55.5` </details> <details> <summary>chore(deps): update module github.com/rs/zerolog to v1.33.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-rs-zerolog-1.x` - Merge into: `main` - Upgrade [github.com/rs/zerolog](https://github.com/rs/zerolog) to `v1.33.0` </details> <details> <summary>chore(deps): update module github.com/stretchr/testify to v1.9.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-stretchr-testify-1.x` - Merge into: `main` - Upgrade [github.com/stretchr/testify](https://github.com/stretchr/testify) to `v1.9.0` </details> <details> <summary>chore(deps): update module github.com/urfave/cli/v2 to v2.27.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/github.com-urfave-cli-v2-2.x` - Merge into: `main` - Upgrade [github.com/urfave/cli/v2](https://github.com/urfave/cli) to `v2.27.4` </details> <details> <summary>chore(deps): update module golang.org/x/crypto to v0.27.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/golang.org-x-crypto-0.x` - Merge into: `main` - Upgrade golang.org/x/crypto to `v0.27.0` </details> <details> <summary>chore(deps): update dependency mkdocs-material to v9</summary> - Schedule: ["at any time"] - Branch name: `renovate/mkdocs-material-9.x` - Merge into: `main` - Upgrade [mkdocs-material](https://github.com/squidfunk/mkdocs-material) to `~=9.5` </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:94693a990c975907e7f13da3309b9d56ba02b3983519b41786edf5cf031e457c--> Reviewed-on: #1 Co-authored-by: Renovate Bot <renovate@keks.cloud> Co-committed-by: Renovate Bot <renovate@keks.cloud> |
||
---|---|---|
.forgejo/workflows | ||
pkg | ||
vendor | ||
.gitignore | ||
.goreleaser.yaml | ||
go.mod | ||
go.sum | ||
Idun.jpg | ||
main.go | ||
Readme.md | ||
renovate.json |
Idun
A small CLI Tool to clean Backups from different Sources. Based on Rules Idun delete Backup files that are older but keep 1 per hour, per day, per weak or month.
Buckets
Based on the age of a Backup the Backups will be sorted in one Bucket and based on the Rules of that Bucket will be deleted or keep the Backup.
Unlimit Bucket (config per Hour)
Keep every Backup
You can configure that for the first X Hour of a Backup livetime. The number of hours is the minimum Hours Idun keep the Backups
Hourly Bucket (config per Hour)
Will keep one Backup per Hour. One Hour is from Min 0 to Min 59, it will keep the olders Backup. If you make Backups at XX:00, XX:15, XX:30 and XX:45 it will keep the Backup at XX:45.
Daily Backup (config per Day)
Will keep one Backup per Day. One Day is from 00:00:00 UTC to 23:59:59, it also will keep the olders Backup, tha backup closed to 23:59:59 will stay, all newer Backup at that day will be removed.
Weekly Backup (config per Month)buc
Monthly Backups (config per Month)
Delete All
Delete all Backups in this Bucket, used at the end to remove all really old (based on the rules) backups
Backends
Locale Filesystem
Config parameter:
- path: Path to the folder on the Filesystem
SFTP
issues:
- Currenlty just with username/password
- untestet
Config parameter:
- path: Path to the folder on the Filesystem
- username: Username
- password: Password
- addr: Server and Port (server:port)
S3
issues:
- untestet
Config Parameter:
- prefix: Path/S3 Prefix to the Backups
- keyid: API Key Id
- secret: API Key Secret
- bucket: Name of the bucket
- endpoint: Endpoint
- region: Region
Config
---
timezone: Europe/Berlin
jobs:
- name: abc
driver: LocaleFileSystem
buckets:
daily: 3
monthly: 12
hourly: 130
config:
path: /tmp/idun-test
- name: abc2
driver: LocaleFileSystem
buckets:
hourly: 12
config:
path: /tmp/idun-test
- name: name
driver: sftp
buckets:
monthly: 12
weekly: 3
daily: 3
hourly: 24
unlimit: 0
config:
path: /backup
username: USERNAME
password: PASSWORD
addr: SERVER:PORT
- name: git
driver: s3
config:
prefix: git.keks.cloud/forgejo
keyid: KEY
secret: SECRET
bucket: BUCKET
endpoint: https://s3.eu-central-003.backblazeb2.com
region: eu-central-003
buckets:
monthly: 12
weekly: 3
daily: 3
hourly: 24
unlimit: 0
Usage
Show Plan
You can see the Plan to check if the config is what you are expected.
idun plan -job abc2
The job argument is optional and can be used to show just the plan of on job based on the "name" in the config.
Dry-Run
Show all fieles
idun dry-run -job abc2
The job argument is optional and can be used to show just the plan of on job based on the "name" in the config.
Execute
Execute the deletion, will ask before deleting the files
idun execute -job abc2
The job argument is optional and can be used to show just the plan of on job based on the "name" in the config.
Cron run
Execute the deletion, without ask before deleting the files
idun execute -job abc2 -cron
The job argument is optional and can be used to show just the plan of on job based on the "name" in the config.
FAQ
Why minimum Hour/Day/Month
If you configure to keep one backup per hour for 12 hours Idun will make sure there will be hourly backups for at least 12 hours. But based on the rules of the next Buckets, which is per Day from 00:00:00 UTC to 23:59:59 UTC there may be a gap between the end hour of the "Hourly Bucket" and the beginn of the "Daily Bucket", in this case Iduna will not delete the Backup files. So ther will be up to 35 Hours Hourly Backups.