mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Updating is not worth it! #1953
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1953
Loading…
Add table
Add a link
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?
Originally created by @wilcochris on GitHub (Mar 1, 2023).
Copied the data directory as was suggested in the backup section of the dashboard.
Followed the guide to update Uptime Kuma
Restored data directory.
Everything is gone.
How do I get back the work I put into creating the monitors?
If there isn't a way then I will just ditch this as updating the container shouldn't kill all of the setup I have done. Extremely annoyed at this
@github-actions[bot] commented on GitHub (Mar 1, 2023):
@wilcochris: Hello! 👋
This issue is being automatically closed because it does not follow the issue template. Please DO NOT open a blank issue.
DOWNandUP#3112DOWNandUP#3115