Backups for Forgejo #29
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#224 automated dev-ops workflows
fediversity/fediversity
#124 enable back-ups of application database
fediversity/fediversity
#126 Operator can make back-ups of applications' mutable file systems
fediversity/fediversity
Reference
fediversity/fediversity#29
Loading…
Reference in a new issue
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?
We host all sorts of information critical for the project here. While there's probably some default backup scheme working in the background, explicit configuration that is tested automatically -- and at least once manually with production data -- are a baseline requirement for sustainable operations.
c.f. #312
This is not a user story though, it's about infrastructure for development here.
yeah, hence just the reference to the ticket as related, rather than an actual dependency