lunny/helm-chart
1
0
Fork 1
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

Add a way to backup gitea and upload to S3 #1

New Issue
Closed
opened 2020-07-11 15:25:40 +00:00 by MOZGIII · 3 comments
MOZGIII commented 2020-07-11 15:25:40 +00:00 (Migrated from gitea.com)
Copy Link

Gitea is a service that needs redular backups. Would be great if Helm Chart offered a built-in way to run backups and upload the archives to S3.

Gitea is a service that needs redular backups. Would be great if Helm Chart offered a built-in way to run backups and upload the archives to S3.
techknowlogick commented 2020-07-12 03:29:27 +00:00 (Migrated from gitea.com)
Copy Link

Utilizing backup tools, such as mysqldump/pg_dump for database (crunchydata has a good one for postgres operator), and restic for repos on disk, may be a better approach than adding in backups into the chart, as you can leverage things such as incremental backups, etc..

This is however my opinion, and so I will leave this open in case someone would like to send a PR for this ticket.

Utilizing backup tools, such as mysqldump/pg_dump for database (crunchydata has a good one for postgres operator), and restic for repos on disk, may be a better approach than adding in backups into the chart, as you can leverage things such as incremental backups, etc.. This is however my opinion, and so I will leave this open in case someone would like to send a PR for this ticket.
sstubbs commented 2020-08-23 17:47:32 +00:00 (Migrated from gitea.com)
Copy Link

An integrated backup solution would be great for the database. Perhaps it would also be good idea to change the deployment https://gitea.com/gitea/helm-chart/src/branch/master/templates/deployment.yaml to a statefulset so velero can do incremental backups.

An integrated backup solution would be great for the database. Perhaps it would also be good idea to change the deployment https://gitea.com/gitea/helm-chart/src/branch/master/templates/deployment.yaml to a statefulset so velero can do incremental backups.
sstubbs commented 2020-08-23 18:55:32 +00:00 (Migrated from gitea.com)
Copy Link

An integrated backup solution would be great for the database. Perhaps it would also be good idea to change the deployment https://gitea.com/gitea/helm-chart/src/branch/master/templates/deployment.yaml to a statefulset so velero can do incremental backups.

Nevermind I see it is a statefulset now.

> An integrated backup solution would be great for the database. Perhaps it would also be good idea to change the deployment https://gitea.com/gitea/helm-chart/src/branch/master/templates/deployment.yaml to a statefulset so velero can do incremental backups. Nevermind I see it is a statefulset now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
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 Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lunny
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#1
No description provided.
Delete Branch "%!s()"

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?