Run scheduled backups using the Gitea dump function #152
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#152
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "ericbram/helm-chart:master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Backups are unfortunately not built in to the list of cron tasks made available by
Gitea
. While it's possible that in the future, backups will be added to the list of cron tasks, there's no current implementation. However,Gitea
does provide a CLI commanddump
to execute this action.This PR is used simply to construct a
dump
command based on the list of available options from the CLI, and following the recommendations from Gitea Backup and Restore.It generates a ConfigMap script that gets placed in the appropriate
/etc/periodic
directory based on the backupschedule
variable, which the pod executes accordingly. This can be used in conjunction with theextraVolumes
/extraVolumeMounts
to backup to persistent storage.Hmm actually it looks like
crond
isn't running by default on my test container -- I've just been manually running whatcron
would call. I'll see if there's a sufficient way to remedy.Pull request closed