SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01recondistro and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
2. 02reconSyncthing already installed? which version?
3. 03recondoes a syncthing@… service already exist, and for which user?
4. 04reconport 8384 (GUI) already taken, and by what? empty = free; taken → ask for another port (ask_user)
5. 05reconport 22000 (sync) already taken, and by what? empty = free; taken → ask for another port (ask_user)
6. 06reconis a firewall (ufw or firewalld) active?
7. 07actAdd the official repository (Debian/Ubuntu) or EPELverify
8. 08actInstall Syncthingverify
9. 09actCreate the user (only if it does not exist)verify
10. 10actEnable the syncthing@user serviceverify
11. 11actProtect the GUI with a passwordverify
12. 12actThe GUI responds locallyverify
13. 13actOpen the sync ports (only if a firewall is active)verify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyAdd the official repository (Debian/Ubuntu) or EPELVerified byapt-cache policy syncthing 2>/dev/null | grep -c apt.syncthing.net || dnf info syncthing 2>/dev/null | grep -c Version
2. 02verifyInstall SyncthingVerified bysyncthing --version
3. 03verifyCreate the user (only if it does not exist)Verified byid -u ${user}
4. 04verifyEnable the syncthing@user serviceVerified bysystemctl is-active syncthing@${user}
5. 05verifyProtect the GUI with a passwordVerified bysudo -H -u ${user} syncthing cli config gui user get
6. 06verifyThe GUI responds locallyVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8384/rest/noauth/health
7. 07verifyOpen the sync ports (only if a firewall is active)Verified byufw status 2>/dev/null | grep ALLOW; firewall-cmd --list-ports 2>/dev/null; true

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

SEC.05

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.06

Deploy on Servor button

Maintain Syncthing or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More self-hosted recipes

1. 01VaultwardenVaultwarden password manager (Bitwarden-compatible) via Docker Compose, over HTTPS when a domain is provided.
2. 02GiteaLightweight Gitea Git forge via Docker Compose (SQLite), web on localhost, Git SSH on a dedicated port.
3. 03Uptime KumaUptime Kuma 2 uptime monitoring via Docker Compose, over HTTPS when a domain is provided.
4. 04NextcloudNextcloud (file cloud) via Docker Compose: PostgreSQL, Redis, cron, admin created automatically.
5. 05JellyfinJellyfin media server via Docker Compose, media folder mounted read-only, HTTPS when a domain is provided.