2.1.3

This release packs all the upstream changes and preserves all features introduced as part of Replicator Kuma.

Internally, the repo moves from copying the entire monitor.js file to patching the upstream file at build time.

Spooky 2.0.2 🎃

🎃 Replicator Kuma V2.0.2 🏳️‍🌈

Uptime Kuma v2 has gone stable! This release packs all the upstream changes and preserves all features introduced as part of Replicator Kuma

Happy Halloween, keep it spooky! 👻

2.0.0-beta.4

Replicator Kuma V2 🏳️‍🌈

This release is a drop-in replacement if you are using uptime-kuma v2, if you are using v1, check the readme for the upgrade guide.

Major Changes

New Replication Engine (v2):

The replication engine has been completely rewritten to be more robust and flexible. It now uses a CSV-based approach and supports different database backends (SQLite, MariaDB, and embedded MariaDB).

You can use different database backends for leader and followers and swap the backend for another as long as you don't mind loosing monitoring history (check Readme).

Local Entity Replication:

Support for Local Entity Replication has been added to handle entities that should be local to each instance.

When this is enabled, the leader's Local Entity is replicated to the followers but any changes made to them are preserved (ex: you can change a proxy's URL and it won't be updated).

Each instance's proxy or remote browser can be individually managed, the replication for all other entities remain unchanged.
The following are treated as local entities:

• proxy
• remote_browser

Note the following caveats (this takes proxy as an example but the same applies to remote browser):

1. If a leader adds or deletes a proxy, this will be replicated to the proxy.

   A. This also means that one monitor cannot have proxy configured on the leader and not the follower (or vice versa)

2. If the leader updates a proxy while its value was never updated on the follower, the follower will continue to have the old value.

   A. If you want to update the value across all followers, deleting the proxy, create a new proxy and configure the monitor to use the new proxy will update it for all followers.

3. Local Entity replication is enabled for both entities, you can't choose to use it for proxy and not remote browser.

The default behaviour is to treat Local Entities as a regular entity and replace the values on the follower, it must be enabled per follower.

To enable local entity replication, set the REPLICATOR_MODE variable on the follower to RESTORE_LOCAL_ENTITY_REPLICATION.

As always, the newest docker image can be found on Docker Hub:
https://hub.docker.com/repository/docker/realsidsun/replicator-kuma

v1.23.16-2 - wrapping up v1

Final v1 release 🎀

This release wraps uptime-kuma / replicator-kuma v1 in a nice pretty bow 🎀

Specifically, it adds hostname to certificate expiry notifications on replicator-kuma's side, everything else remains the same.

As always, the newest docker image can be found on Docker Hub:
https://hub.docker.com/repository/docker/realsidsun/replicator-kuma