29 Commits

Author SHA1 Message Date
dfed87a39f missing replacement 2026-04-05 14:50:03 +00:00
8aaafecf5b add missing content again 2026-04-05 14:49:20 +00:00
3b2a3fc5e9 chore: publish 3.0.0+2.2.1 release 2026-04-02 15:02:04 +02:00
e59db61344 Revert "chore: publish 2.1.0+2.2.1 release"
This reverts commit 4be91e3fe6.
2026-04-02 14:47:37 +02:00
4be91e3fe6 chore: publish 2.1.0+2.2.1 release 2026-04-01 18:38:13 +02:00
b21ab2c07e Revert "chore: publish 2.1.0+2.2.1 release"
This reverts commit 4493f6ad6c.
2026-04-01 18:37:11 +02:00
ba9e059039 increase entrypoint version 2026-04-01 18:29:38 +02:00
4493f6ad6c chore: publish 2.1.0+2.2.1 release 2026-04-01 18:25:05 +02:00
ce907a3c4a Revert "chore: publish 2.1.0+2.2.1 release"
This reverts commit 69a0443f6e.
2026-04-01 18:24:15 +02:00
5fc90c6386 Revert "Revert "rework recipe and upgrade kuma version""
This reverts commit 7897cae890.
2026-04-01 18:14:58 +02:00
69a0443f6e chore: publish 2.1.0+2.2.1 release 2026-04-01 17:35:02 +02:00
31a4e77938 Merge pull request 'setup maintenance for repo' (#9) from maintainer into main
Reviewed-on: https://git.coopcloud.tech/coop-cloud/uptime-kuma/pulls/9
2026-04-01 15:08:41 +00:00
ea9e14c357 add standard reviewer 2026-04-01 14:53:28 +00:00
1876e3555d added recipe linting 2026-04-01 06:33:57 +00:00
564441ab06 add pull request template 2026-03-31 18:47:09 +02:00
7897cae890 Revert "rework recipe and upgrade kuma version"
This reverts commit 773fdeb412.
2026-03-31 18:06:19 +02:00
f41d89d320 adding information for maintainership 2026-03-31 17:58:55 +02:00
773fdeb412 rework recipe and upgrade kuma version 2026-03-31 17:42:37 +02:00
59ed487328 upgrade to latest version 2.2.1 2026-03-31 16:25:12 +02:00
ca67375a56 chore: update image tags 2026-03-27 18:00:24 +01:00
b51e8f8f45 Merge pull request 'Added backup flags to compose.yml' (#4) from bb2-backups into main
Reviewed-on: https://git.coopcloud.tech/coop-cloud/uptime-kuma/pulls/4
2025-06-05 15:26:01 +00:00
436014726c Added mariadb bb2 labels to compose.yml 2025-04-01 18:00:39 +01:00
cc408eb56a Set backups to YES in README 2025-04-01 17:58:36 +01:00
65e0407ed7 Added backup flags to compose.yml 2025-04-01 17:55:31 +01:00
a2fc13d45b feat: add command to list all monitored urls 2025-03-04 20:57:04 +01:00
185e2f4fe8 chore: publish 2.0.0+2.0.0-beta.1 release 2025-02-26 17:00:14 +01:00
61d122b455 feat: switch to upstream image (#3)
Reviewed-on: https://git.coopcloud.tech/coop-cloud/uptime-kuma/pulls/3
Reviewed-by: yksflip <flip@yksflip.de>
Co-authored-by: p4u1 <p4u1_f4u1@riseup.net>
Co-committed-by: p4u1 <p4u1_f4u1@riseup.net>
2025-02-26 15:57:07 +00:00
769b0bdf2b Update .drone.yml 2025-01-08 10:09:13 -08:00
83b4479bb6 chore: publish 1.0.2+latest release 2024-11-14 14:18:24 +01:00
12 changed files with 156 additions and 51 deletions

View File

@ -32,7 +32,7 @@ steps:
from_secret: drone_abra-bot_token
fork: true
repositories:
- coop-cloud/auto-recipes-catalogue-json
- toolshed/auto-recipes-catalogue-json
trigger:
event: tag

View File

@ -1,4 +1,6 @@
TYPE=uptime-kuma
COMPOSE_FILE="compose.yml"
LETS_ENCRYPT_ENV=production
DOMAIN=uptime-kuma.example.com
@ -8,4 +10,8 @@ DOMAIN=uptime-kuma.example.com
SECRET_DB_PASSWORD_VERSION=v1
SECRET_DB_ROOT_PASSWORD_VERSION=v1
LETS_ENCRYPT_ENV=production
## Enable mariadb, otherwise sqlite will be used
#COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
# only for testing branches of uptime-kuma
#UPTIME_KUMA_GH_REPO=<branch name>

View File

@ -0,0 +1,17 @@
---
name: "Uptime Kuma pull request template"
about: "Uptime Kuma pull request template"
---
<!--
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.
-->
* [ ] I have deployed and tested my changes
* [ ] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
* [ ] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
* [ ] 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)

32
MAINTENANCE.md Normal file
View File

@ -0,0 +1,32 @@
# Uptime Kuma Recipe Maintenance
All contributions should be made via a pull request. This is to ensure a
certain quality and consistency, that others can rely on.
## Maintainer Responsibilities
A recipe maintainer has the following responsibilities:
- Respond to pull requests / issues within a week
- Make image security updates within a day
- Make image patch / minor updates within a week
- Make image major updates within a month
In order to fullfill these responsibilities a recipe maintainer:
- Has to watch the repository (to get notifications)
- Needs to make sure renovate is configured properly
## Pull Requests
A pull request can be merged if it is approved by at least one maintainer. For
pull requests opened by a maintainer they need to be approved by another
maintainer. Even though it is okay to merge a pull request with one approval, it
is always better if all maintainers looked at the pull request and approved it.
## Become a maintainer
Everyone can apply to be a recipe maintainer:
1. Watch the repository to always get updates
2. Simply add your self to the list in the [README.md](./README.md) and open a new pull request with the change.
3. Once the pull request gets merged you will be added to the [uptime kuma maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/uptime-kuma-maintainers).

View File

@ -1,14 +1,19 @@
# 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**: No
* **Backups**: No
* **Healthcheck**: Yes
* **Backups**: Yes
* **Email**: No
* **Tests**: No
* **SSO**: No
@ -22,3 +27,10 @@
* `abra app deploy <app-name>`
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:
```
#COMPOSE_FILE="$COMPOSE_FILE:compose.mariadb.yml"
```

View File

@ -1 +1,5 @@
export APP_ENTRYPOINT_VERSION=v2
export APP_ENTRYPOINT_VERSION=v3
get_all_urls() {
echo "select url from monitor" | mariadb -u kuma -p$(cat /run/secrets/db_password) -D kuma | sed 's|https://||' | sed 's|/.*||' | sort
}

59
compose.mariadb.yml Normal file
View File

@ -0,0 +1,59 @@
---
version: "3.8"
services:
app:
secrets:
- db_password
networks:
- internal
environment:
- UPTIME_KUMA_DB_TYPE=mariadb
- UPTIME_KUMA_DB_HOSTNAME=db
- UPTIME_KUMA_DB_PORT=3306
- UPTIME_KUMA_DB_NAME=kuma
- UPTIME_KUMA_DB_USERNAME=kuma
- UPTIME_KUMA_DB_PASSWORD_FILE=/run/secrets/db_password
depends_on:
- db
db:
image: mariadb:11.8
environment:
- MYSQL_ROOT_PASSWORD_FILE=/run/secrets/db_root_password
- MYSQL_PASSWORD_FILE=/run/secrets/db_password
- MYSQL_USER=kuma
- MYSQL_DATABASE=kuma
volumes:
- mariadb:/var/lib/mysql
networks:
- internal
secrets:
- db_password
- db_root_password
deploy:
labels:
backupbot.backup: "${ENABLE_BACKUPS:-true}"
backupbot.backup.pre-hook: "mariadb-dump --single-transaction -u root -p\"$$(cat /run/secrets/db_root_password)\" kuma | gzip > /var/lib/mysql/dump.sql.gz"
backupbot.backup.volumes.mariadb.path: "dump.sql.gz"
backupbot.restore.post-hook: "gzip -d /var/lib/mysql/dump.sql.gz && mariadb -u root -p\"$$(cat /run/secrets/db_root_password)\" kuma < /var/lib/mysql/dump.sql && rm -f /var/lib/mysql/dump.sql"
healthcheck:
test: ["CMD-SHELL", 'mariadb-admin -p"$$(cat $MYSQL_ROOT_PASSWORD_FILE)" ping']
interval: 30s
timeout: 10s
retries: 10
start_period: 1m
volumes:
mariadb:
networks:
internal:
secrets:
db_password:
external: true
name: ${STACK_NAME}_db_password_${SECRET_DB_PASSWORD_VERSION}
db_root_password:
external: true
name: ${STACK_NAME}_db_root_password_${SECRET_DB_ROOT_PASSWORD_VERSION}

View File

@ -3,33 +3,20 @@ version: "3.8"
services:
app:
image: git.coopcloud.tech/coop-cloud-chaos-patchs/uptime-kuma:latest
image: louislam/uptime-kuma:2.2.1
volumes:
- data:/app/data
secrets:
- db_password
networks:
- internal
- proxy
environment:
- UPTIME_KUMA_GH_REPO=louislam:uptime-kuma
- UPTIME_KUMA_DB_TYPE=mariadb
- UPTIME_KUMA_DB_HOSTNAME=db
- UPTIME_KUMA_DB_PORT=3306
- UPTIME_KUMA_DB_NAME=kuma
- UPTIME_KUMA_DB_USERNAME=kuma
- UPTIME_KUMA_DB_PASSWORD_FILE=/run/secrets/db_password
depends_on:
- db
- UPTIME_KUMA_GH_REPO
- UPTIME_KUMA_DB_TYPE=sqlite
configs:
- source: app_entrypoint
target: /docker-entrypoint.sh
mode: 0555
entrypoint: /docker-entrypoint.sh
deploy:
update_config:
failure_action: rollback
order: start-first
labels:
- "traefik.enable=true"
- "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=3001"
@ -40,44 +27,21 @@ services:
#- "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect"
#- "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true"
#- "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}"
- "coop-cloud.${STACK_NAME}.version=1.0.1+latest"
- "coop-cloud.${STACK_NAME}.version=3.0.0+2.2.1"
- "backupbot.backup=${ENABLE_BACKUPS:-true}"
healthcheck:
test: "curl -L localhost:3001'"
test: "curl -L localhost:3001"
interval: 30s
timeout: 10s
retries: 5
start_period: 2m
db:
image: mariadb:11.5
environment:
- MYSQL_ROOT_PASSWORD_FILE=/run/secrets/db_root_password
- MYSQL_PASSWORD_FILE=/run/secrets/db_password
- MYSQL_USER=kuma
- MYSQL_DATABASE=kuma
volumes:
- mariadb:/var/lib/mysql
networks:
- internal
secrets:
- db_password
- db_root_password
volumes:
mariadb:
data:
networks:
proxy:
external: true
internal:
secrets:
db_password:
external: true
name: ${STACK_NAME}_db_password_${SECRET_DB_PASSWORD_VERSION}
db_root_password:
external: true
name: ${STACK_NAME}_db_root_password_${SECRET_DB_ROOT_PASSWORD_VERSION}
configs:
app_entrypoint:

View File

@ -24,7 +24,7 @@ file_env() {
unset "$fileVar"
}
file_env "UPTIME_KUMA_DB_PASSWORD"
#file_env "UPTIME_KUMA_DB_PASSWORD"
# upstream startup command
cd /app

View File

@ -0,0 +1 @@
sqlite is the default database now, check the README.md on how to configure mariadb

1
release/3.0.0+2.2.1 Normal file
View File

@ -0,0 +1 @@
In case you are currently using MariaDb instead of the internal sqlite, you need to activate the usage of compose.mariadb.yaml in your env file. (compare .env.sample) Reason for this is that the mariadb container was removed from compose.yml

9
renovate.json Normal file
View File

@ -0,0 +1,9 @@
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended"
],
"reviewers": [
"stevensting"
]
}