Uptime Kuma 2.0.0 package

[luckow]

@joseph maybe. But first I have to fix this: Trace: [Error: select * from heartbeat where monitor_id = 75 ORDER BY time DESC limit 1 - SQLITE_CORRUPT: database disk image is malformed] This is a log entry BEFORE the 2.0 update.

[andreasdueren]

@joseph Yes, upgrade worked fine for me too. Took forever, probably almost an hour but I'm running it on a super low powered VPS. Does that mean no more embedded Chromium or did you package it in? Not using it, just curious.

[Lanhild]

I've opened an issue upstream, as starting the update triggered a false positive alert from Google Chrome on my subdomain:

• https://github.com/louislam/uptime-kuma/issues/6223

[luckow]

Woohoo. 2.0.1 update worked.
Q: Any plans to switch the app package to MariaDB instead of sqlite?

[Lanhild]

@luckow I don't believe we have a MariaDB addon.

[Lanhild]

Fixed with https://github.com/louislam/uptime-kuma/releases/tag/2.0.2.

[nebulon]

just to update here, package for version 2.0.2 is out

[matix131997]

Today, I read about it on GitHub and the Uptime Kuma demo page shows the possibility of connecting MySQL. So, it is possible to bundle Uptime Kuma with MySQL.

https://demo.kuma.pet/start-demo

[james]

Hello @matix131997
Thanks for information. We will look into it.

[james]

Took a little peek into the MariaDB/MySQL support of Uptime Kuma https://github.com/louislam/uptime-kuma/wiki/Environment-Variables#mariadb-environment-variables
Unfortunately the official statement is that migrating an existing SQLite database to MariaDB is not supported.
But, there is a way and someone did the work already https://github.com/louislam/uptime-kuma/issues/5280#issuecomment-2642224548
How stable this approach is needs to be verified.