Feature request: Ability to create a primary caprover on one VPS and a backup caprover on a second VPS

[Raytle]

I read.... https://caprover.com/docs/backup-and-restore.html

The following is not a perfect solution. But the perfect is the enemy of the good.

I would like to install caprover on two separate VPSes, say, for example at Hetzner and Vultr. I imagine that my Hetzner VPS would be my "primary" caprover and that my Vultr VPS would be my "backup" caprover.

I would like be able to configure each application running on my primary caprover so that every X minutes, application Y's data would be copied from my primary caprover to my backup caprover. I might, for example, configure some applications to copy data from my primary caprover to my backup caprover every 30 minutes, others every 5 hours, and others every 24 hours.

I know it's fun to talk about stuff like Chapter 25. High Availability, Load Balancing, and Replication, but I imagine implementing most of those features for caprover would be too much work at this time. I'm thinking of a far more mundane yet nonetheless useful feature.

I do not imagine that this feature would replace ordinary backups; rather I imagine it would complement them. See, I would like to be able to very quickly and very easily verify that I actually had working backups. As you must know, people frequently believe they have working backups when in fact they don't. Therefore, I envision that I would simply login to a couple of my applications of my backup caprover and compare a few samples of the data to the data on my primary caprover.

Secondly, I imagine that sometimes I might be able to solve a problem I was having by transforming my backup caprover to my primary caprover. Obviously this would not always be helpful (for example, when my backup caprover had the same problem as my primary caprover) but it would probably be helpful sometimes. I imagine that if I were to have a problem with my primary caprover I would probably shut it down (or perhaps even destroy it) and transform my backup caprover into my new primary caprover. Then I would create a new backup caprover to replace my old backup caprover (which had become my new primary caprover).

Because VPSes are very inexpensive, for many users of caprover it would probably be worthwhile to have two (or perhaps even more) instances of caprover running simultaneously: a primary caprover and a backup caprover (or perhaps even two or more backup caprovers).

It seems to me that the fundamental problem is a linguistic one: people tend to refer to "my server" or "the server" when they should say, for example, "my primary server" or "the primary server".

Just shy of a hundred years or ago, millions of people started saying, "Switch on the wireless." They were, of course, referring to "the radio." In the 1920's radios were large, heavy, and expensive. Families that had a radio normally only owned one radio. Therefore, saying "switch on the wireless" made sense. As radios became cheaper and cheaper instead of saying the "the wireless" millions of people began to say "the radio in the kitchen" or "the radio in the living room".