Add uptime kuma as a service we can deploy to a different host for monitoring. #196
No reviewers
Labels
No labels
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/ansible#196
Loading…
Reference in a new issue
No description provided.
Delete branch "add_uptime_data_coop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Running on https://uptime.data.coop with a status page on https://status.data.coop
I guess this is fixing #55 ?
@valberg I've made some improvements to not specify service settings twice:
services_exclude
defaults to an empty listservices_include
defaults to all services that are not inservices_exclude
uptime_kuma
settings is added toroles/docker/defaults/main.yml
services_include
is used inuptime.data.coop.yml
to only includenginx_proxy
anduptime_kuma
services_exclude
is used inplaybook.yml
to excludeuptime_kuma
services_include
are deployedWhat do you think? 🙂