If you plan to regularly add repos to the config file, I would put the config file in a repo, and sync that with Hesokuri. That way, when you create a new repo, you only have about two more steps before the repo is on every peer. Here's how it works:
- [Before starting Hesokuri, you set the HESOCFG environment var to something like ~/some-git-repo/hesocfg]
- You edit the config file with the new repo
- Hesokuri automatically reads the changed config and starts managing the new repo
- You commit the config file
- Hesokuri pushes the config file to the other peers
- Hesokuri (running on the other peers) merges the new config file
- Similar to step 3, the other peers automatically see the changed config file and restart
Hopefully that work flow will be good enough for you for the time being.
Thanks,
Matt