From f41d89d3207a5acdc829fed5d501801360b5ec08 Mon Sep 17 00:00:00 2001
From: stevensting <stefan@klasse-methode.it>
Date: Tue, 31 Mar 2026 17:58:55 +0200
Subject: [PATCH] adding information for maintainership

---
 MAINTENANCE.md |  0
 README.md      | 13 +++++++++----
 renovate.json  |  6 ++++++
 3 files changed, 15 insertions(+), 4 deletions(-)
 create mode 100644 MAINTENANCE.md
 create mode 100644 renovate.json

diff --git a/MAINTENANCE.md b/MAINTENANCE.md
new file mode 100644
index 0000000..e69de29
diff --git a/README.md b/README.md
index e046d08..d354e31 100644
--- a/README.md
+++ b/README.md
@@ -1,11 +1,16 @@
 # uptime-kuma
 
-> One line description of the recipe
+[![Build Status](https://build.coopcloud.tech/api/badges/coop-cloud/uptime-kuma/status.svg)](https://build.coopcloud.tech/coop-cloud/uptime-kuma)
+
+
+> A fancy self-hosted monitoring tool 
 
 <!-- metadata -->
 
-* **Category**: Apps
-* **Status**: 0
+* **Maintainer**: [@stevensting](https://git.coopcloud.tech/stevensting)
+* **Status**: `stable`
+* **Category**: Utilities
+* **Features**: ?
 * **Image**: [`uptime-kuma`](https://hub.docker.com/r/uptime-kuma), 4, upstream
 * **Healthcheck**: Yes
 * **Backups**: Yes
@@ -25,7 +30,7 @@ For more, see [`docs.coopcloud.tech`](https://docs.coopcloud.tech).
 
 ## MariaDB
 
-By default uptime-kuma uses a sqlite database. It is possible to switch to a 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"
 ```
diff --git a/renovate.json b/renovate.json
new file mode 100644
index 0000000..5db72dd
--- /dev/null
+++ b/renovate.json
@@ -0,0 +1,6 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "config:recommended"
+  ]
+}