Are you able to inject a secondary moon in to the config before the workflow is run

[nhaskel]

I have a secondary server set up as a moon and I would like to add its identity to the moon.json file that is generated in the workflow. Would this be possible to add in to the patch file?

Thank you

[kkkgo]

The .moon node files for ZeroTier do not need to be placed on the planet server; they can be operational when placed in the /var/lib/zerotier-one/moons.d/ directory on both the client and moon nodes. Of course, the moon node also needs to replace the planet. The signing of Moon.json (zerotier-idtool genmoon moon.json) can be executed on any ZeroTier terminal, but the moon.json generated in the previous step is generally run on the moon node to obtain that node's identity (zerotier-idtool initmoon /var/lib/zerotier-one/identity.public). If you are running ZeroTier with Docker, you can map and mount the /var/lib/zerotier-one/moons.d/ folder.

[nhaskel]

Thanks for the info, just to be clear is it recommended to have multiple moon nodes with the planet server or is the standalone (private) planet server sufficient to host/control multiple networks? I've tried to piece this information together and all the sources I have found are using the Zerotier root planets instead of a private planet and they suggest having at least 2 moon servers.

Thanks for your work piecing this together.