850a01ab34
<!-- Thank you for doing recipe maintenance work! Please mark all checklist items which are relevant for your changes. Please remove the checklist items which are not relevant for your changes. Feel free to remove this comment. --> * [x] I have deployed and tested my changes * [x] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash) * [x] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes) * [x] I ran `abra recipe lint uptime-kuma --chaos` on the PR's branch and fixed the warnings. * [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes) Reviewed-on: https://git.coopcloud.tech/coop-cloud/uptime-kuma/pulls/14 Co-authored-by: stevensting <stefan@klasse-methode.it> Co-committed-by: stevensting <stefan@klasse-methode.it>
uptime-kuma
A fancy self-hosted monitoring tool
- Maintainer: @stevensting
- Status:
stable - Category: Utilities
- Features: ?
- Image:
uptime-kuma, 4, upstream - Healthcheck: Yes
- Backups: Yes
- Email: No
- Tests: No
- SSO: No
Quick start
abra app new uptime-kuma --secretsabra app config <app-name>abra app deploy <app-name>
For more, see docs.coopcloud.tech.
MariaDB
By default uptime-kuma uses a sqlite database. It is possible to switch to a mariadb by:
#COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"