Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to extract Monitors from an Docker image of Uptime Kuma? #3833

Closed
2 tasks done
akolar123 opened this issue Oct 2, 2023 · 6 comments
Closed
2 tasks done
Labels

Comments

@akolar123
Copy link

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Is it possible to extract Monitors from an Docker image of Uptime Kuma?

In what directory are the Monitors stored in and is it possible to migrate them to a different Uptime Kuma server (I have switcehd from Docker to Windows Portable version)?

I'm not able to create a backup as I can not access the previous instance of Uptime Kuma, but I have created an Docker Image before my server crashed.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.1

💻 Operating System and Arch

Windows Portable

🌐 Browser

Brave

🐋 Docker Version

No response

🟩 NodeJS Version

No response

@akolar123 akolar123 added the help label Oct 2, 2023
@Zaid-maker
Copy link
Contributor

You can copy the ./data/ folder and paste it into your new Uptime Kuma and u are good to go!

@devunderslash
Copy link

You could also export the monitor json via the settings -> Backup -> Export Backup which allows you could use to also Import for Disaster Recovery purposes.

@CommanderStorm
Copy link
Collaborator

@devunderslash as warned on the site you mentioned, the backup feature has been left unmaintained for quite some time.
Please make a backup of the database instead by shutting down uptime-kuma and copying the data folder.

See
image

@regchanuk
Copy link

Will back up be updated or removed from the system instead or revamped updated again

@CommanderStorm
Copy link
Collaborator

See #2667

@CommanderStorm
Copy link
Collaborator

Closing as backup has been dropped lacking maintenance in v2.0
A new attempt must be developed with the native backup feature of the db used (sqlite/mariadb) in mind instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants