mastermindzh/rickvanlieshout.com
1
0
Fork 0
mirror of https://github.com/mastermindzh/rickvanlieshout.com synced 2025-07-27 12:42:28 +02:00
Code Issues Packages Projects Releases Wiki Activity

chore: update

Browse Source
This commit is contained in:
Rick van Lieshout
2025-07-15 17:28:41 +02:00
parent c7ef1146b3
commit 7c93cd76d9
38 changed files with 6306 additions and 11016 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/posts/2025/infrastructure-as-code-uptime-monitoring/index.md
View File

@@ -44,7 +44,7 @@ One of the most satisfying aspects of IaC is the ability to automate even the sm
Setting up UptimeKuma is straightforward, you can simply use our old friend Docker:
```docker run -d --name uptime-kuma -v ./data/uptimekuma:/app/data -p 3001:3001 louislam/uptime-kuma```
`docker run -d --name uptime-kuma -v ./data/uptimekuma:/app/data -p 3001:3001 louislam/uptime-kuma`
And access the Dashboard by navigating to <http://localhost:3001> to configure your monitors.
But that isn't automatic enough for me, I like to put my things in compose files for home usage.
@@ -65,8 +65,8 @@ labels:
This actually does 2 things:
- creates a group with the *key/id* `monitoring` and the name `Monitoring`
- Adds a monitor with the *key/id* `uptime_kuma` to UptimeKuma with the type `http`, name `Kuma status monitoring`, and url `http://${HOST_IP}:3001`
- creates a group with the _key/id_ `monitoring` and the name `Monitoring`
- Adds a monitor with the _key/id_ `uptime_kuma` to UptimeKuma with the type `http`, name `Kuma status monitoring`, and url `http://${HOST_IP}:3001`
Adding these labels, whilst AutoKuma is running and configured to pick up labels starting with `kuma` is enough for monitors to show up (after restarting the containers).
All in all, my `docker-compose.yml` file for both UptimeKuma and AutoKuma now looks like this: