From 48dff12fcdafbcb858a945743b5b1d2895fa41b3 Mon Sep 17 00:00:00 2001 From: Sid Sun Date: Fri, 16 Aug 2024 17:29:59 +0530 Subject: [PATCH] add docker image from hub Signed-off-by: Sid Sun --- README.md | 6 ++++++ docker-compose.yaml | 7 ++----- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 6a1d727..6766f24 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,12 @@ This is an extension of the uptime-kuma project to solve this. Replicator Kuma r Replicator Kuma only creates restic snapshots of files (data) when they change change (the data for heartbeats, TLS, settings, etc. i.e. monitoring and instance specific data is not replicated) this selective backup happens by leveraging SHA256 sums - we dump the data and compare latest snapshot data with the new dump. +### Getting started + +Replicator Kuma only adds a script to the original uptime-kuma images, the new images are published to docker hub under realsidsun/replicator-kuma and follows the same semver number as uptime-kuma (starting from 1.23.13). + +Replicator Kuma may lag behind uptime kuma as the repo needs to be manually updated right now (if you notice a new update, fell free to raise a PR updating Dockerfile, the actions workflow should build and push once I merge). + ### How it works Alongside the uptime-kuma service, the replicator kuma container periodically runs a few functions to either: diff --git a/docker-compose.yaml b/docker-compose.yaml index 0aa1d4d..3cd07c3 100644 --- a/docker-compose.yaml +++ b/docker-compose.yaml @@ -3,10 +3,7 @@ version: '3.8' services: main: container_name: uptime-kuma-main - image: replicator-kuma - # build: - # context: . - # dockerfile: Dockerfile + image: realsidsun/replicator-kuma:1.23.13 volumes: - uptime-kuma-main:/app/data:rw ports: @@ -20,7 +17,7 @@ services: - RESTIC_PASSWORD=I9n7G7G0ZpDWA3GOcJbIuwQCGvGUBkU5 replica: container_name: uptime-kuma-replica - image: replicator-kuma + image: realsidsun/replicator-kuma:1.23.13 volumes: - uptime-kuma-replica:/app/data:rw ports: