Hello, I need help designing the correct Syncthing setup for my use-case. I am running Syncthing 1.28.0 on openSUSE (root system service) and Syncthing-Fork on VollaOS (Android 13, de-Googled).
What I want to achieve
I have one folder on the phone:
/storage/emulated/0/DCIM/Camera
I want to sync it to my Linux server in a way that gives me:
-
A real-time mirror of the phone’s files (so I can delete photos on the phone from the computer)
-
A permanent archive, where all files are kept even if deleted from the mirror or deleted on the phone
In short:
Phone folder → Server mirror (2-way sync)
Phone folder → Server archive (never delete anything)
What I tried
-
I created a second folder on the server (“archive”) and checked “Share With → phone” when creating it.
-
But the Android device never receives a folder offer, and the server-side folder remains visible only locally.
-
The phone only shows the original folder, no request to choose a path.
-
“Receive folder offers” is enabled.
-
Syncthing is running (not paused).
-
Both devices sync fine for the first folder.
My questions
-
Is it possible to sync a single source folder on the phone into two different server folders (mirror + archive) using Syncthing alone?
-
If not, what is the recommended Syncthing way to maintain a permanent backup of deleted files while keeping a live mirror that I can delete from?
-
Is File Versioning on the server the correct method for this scenario?
-
Why does the Android device never show the “new folder offered” dialog when the server shares a second folder with it?
-
Is this expected behavior because two folder IDs would point to the same path on Android?
-
Is there a log to check whether the offer was silently rejected?
-
Thank you — I would really appreciate guidance on the correct architecture for this setup.