Uptime Kuma Release 2.0.0 - Stable Release (github.com)
from stonkage@aussie.zone to selfhosted@lemmy.world on 20 Oct 20:41
https://aussie.zone/post/25901755

It is a major version update. It contains some breaking changes. Please read the migration guide carefully if you want to upgrade from v1 to v2.

#selfhosted

threaded - newest

datalogen@feddit.dk on 20 Oct 21:18 next collapse

Sort of an ironic day to release an update for such a tool😆

bishoponarope@lemmy.world on 20 Oct 21:43 next collapse

@dear Mr bezos. Plz fix your shit. Sincerely. The uptime bear.

non_burglar@lemmy.world on 20 Oct 22:29 collapse

Why? I don’t think any part of uptimekuma relies on aws…

dabaldeagul@feddit.nl on 20 Oct 22:34 collapse

No but uptime tracking is relevant due to other services being down.

non_burglar@lemmy.world on 20 Oct 23:50 collapse

Ah, I see.

EarMaster@lemmy.world on 21 Oct 08:20 next collapse

Setting aside the funny (if you’re not affected) coincidence of AWS being down I have to say this is an exemplary way on how upgrades should be announced, executed and documented. There is a migration guide, but even if you don’t read it - in most cases the software will take care of it itself. Well done!

cron@feddit.org on 21 Oct 12:07 collapse

Only downside I see is how long it took for version 2.0 to get released. The previous stable release (1.23.16) was released almost one year ago.

cron@feddit.org on 21 Oct 10:01 next collapse

I’ve been using this new version a few weeks now (since beta 3). The most significant advantage is the performance improvement. With 100+ monitors, the “old” version was very sluggish and took a long time to start.

Edit: I migrated my existing install to mariadb following this thread on github.

Appoxo@lemmy.dbzer0.com on 21 Oct 11:53 next collapse

Thank you very much!

clifmo@programming.dev on 21 Oct 12:35 collapse

If your host is using Debian / Raspbian Buster, you should not upgrade. Due to a bug in the libseccomp2 library, it will run into a startup problem. Read more: github.com/louislam/uptime-kuma/issues/41#issueco…

I read this, but it seems to be ARMv7 only, per the issue title. A little wary still, tho my docker host is x86. I guess I’ll try running a stand alone test to see if it boots.