Just wanted to show how I got two remote instances to work with essentially the same Gatus config under the hood.

I have two instances

• One running locally in my homelab
• Another on a VPS

I have Woodpecker set up for CI/CD to push changes on commit to this repository which houses my configs.
https://github.com/lemeow125/gatus

This runs a quick test to see if the config parses correctly (before deploying)
https://github.com/lemeow125/gatus/blob/master/.woodpecker/.test.yml

Then deploys to both local and remote instances
https://github.com/lemeow125/gatus/blob/master/.woodpecker/.deploy_local.yml
https://github.com/lemeow125/gatus/blob/master/.woodpecker/.deploy_remote.yml

The remote deployment step in particular has some commands to remove remote.yaml from the config folder. This stops it from referencing itself as a remote instance.
It also prefixes all groups to have Remote - in front of them, so that they don't lump into the same subsection in the UI.

This lets me have a unified dashboard, and the remote instance to fall back to in case my homelab does go down.
https://stats.06222001.xyz/ (Local)
https://five.06222001.xyz/ (Remote)

I could have probably spun up a feature request for prefixing groups, but I figured this would be faster.