You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You should only use one controller. Networks and members will not sync between multiple roots.
Multiple root servers are useful for better peer-to-peer discovery, especially if you operate in different regions, as well as redundancy for peer discovery if one goes down.
If you need redundancy for the controller, you should set up a fallback server that can take over if the main controller goes down.
For the backup, you can do something like this ( not tested )
# First stop your containers
docker compose down
# List your volumes to find the correct names for zerotier and postgres-data.
docker volume ls
# Backup PostgreSQL data (replace VOLUME_NAME with your postgres volume name)
docker run --rm -v VOLUME_NAME:/source -v $(pwd)/backup:/backup alpine tar czf /backup/postgres-backup.tar.gz /source
# Backup ZeroTier data (replace VOLUME_NAME with your zerotier volume name)
docker run --rm -v VOLUME_NAME:/source -v $(pwd)/backup:/backup alpine tar czf /backup/zerotier-backup.tar.gz /source
It is possible to create multiple self-hosted servers (planets), which is great!
But is is not clear from documentation, how to configure to:
So, if I deploy planet files, which contains multiple of these (dockerized) servers:
Also:
(Asked this at the discussion, but got no answer. That's why I open an issue instead, so it gets included in the docs.)
The text was updated successfully, but these errors were encountered: