From 6910cccc0a56c5bfce202837d57059d59ef7d773 Mon Sep 17 00:00:00 2001
From: joshmen <joshmen@web>
Date: Sat, 18 Sep 2021 20:10:28 +0000
Subject: [PATCH]

---
 ...ust_all_nodes_be_accessible_to_one_another__63__.mdwn | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 doc/forum/Must_all_nodes_be_accessible_to_one_another__63__.mdwn

diff --git a/doc/forum/Must_all_nodes_be_accessible_to_one_another__63__.mdwn b/doc/forum/Must_all_nodes_be_accessible_to_one_another__63__.mdwn
new file mode 100644
index 0000000000..fc06eb437c
--- /dev/null
+++ b/doc/forum/Must_all_nodes_be_accessible_to_one_another__63__.mdwn
@@ -0,0 +1,9 @@
+The [[walkthrough|https://git-annex.branchable.com/walkthrough/#index3h2]] says:
+
+> Notice that both repos are set up as remotes of one another. This lets either get annexed files from the other. You'll want to do that even if you are using git in a more centralized fashion.
+
+This is not always practical. I use a centralized setup where all of my devices sync (manually) with a bare repo on a server at home over the internet. Clients can access the server but the server cannot access the clients.
+
+Is it safe to use Git Annex in this way? Are there any pitfalls or gotchas I should be aware of? Is this setup any more (or less) risky when using a non-bare central repo?
+
+Thanks for this great piece of software!