🚀 go-pugleaf

Hello all.

We have a scenario where we will have about 8 users dial into a central
network from laptops.  When connecting, they will want to replicate their
data to the server database and receive any updates from the server DB.
These updates will be coming from server users as well as the other remote
users.

In other words, the remote users will initiate the replication when they are
ready (probably daily).

I'm still having trouble getting this to work (see my other post) but I'm
optimistic.  When I do get this working, what is the best way to define the
configuration DB?  Ideally, I'd like to have one single configuration DB
(with all schemas) that defines all 2-way replications that the users can
access when they decide to replicate.  But if I have one configuration DB,
how can I initiate only one replication (replication from one remote user to
server) and not trigger the other replications?  (Not all laptop users will
be connected at the same time, which is why they have to initiate the
replication).

Or will I need to have configuration DBs (each with its own schema) on each
laptop that the remote users can access in order to run their replication on
demand?

Or is all this even possible?

Thanks in advance for any insights.
-Mike