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.
- 01recondoes a timer or service with the same name exist? (do not overwrite without backup)
- 02reconis the OnCalendar expression valid? next run?
- 03recondoes the run-as user exist?
- 04recondoes the binary/script exist and is it executable? (absolute path required)
- 05actWrite service + timerverify
- 06actEnable the timerverify
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.
- 01verifyWrite service + timerVerified by
systemd-analyze verify /etc/systemd/system/${name}.service /etc/systemd/system/${name}.timer && echo ok - 02verifyEnable the timerVerified by
systemctl is-active ${name}.timer && systemctl list-timers ${name}.timer --no-legend
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Do not overwrite an existing timer/service without backup. Do not run the task manually without consent (it may be heavy or destructive). Do not touch the existing crontab.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${name} | Name |
| ${command} | Command |
| ${schedule} | OnCalendar |
| ${user} | User |
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Scheduled task (cron) 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.
Dark background
Light background[](https://servor.app/deploy/setup-cron-job)SEC.07
More ci/cd recipes
- 01GitHub Actions RunnerSelf-hosted GitHub Actions runner under a dedicated user, registered as a systemd service.
- 02GitLab RunnerGitLab Runner from the official repo, registered with the Docker or shell executor.
- 03Woodpecker CILightweight Woodpecker CI (server + agent) via Docker Compose, behind an HTTPS reverse proxy.
- 04Ansible (control node)Ansible installed as a control node from the distro packages.
- 05systemd serviceDaemonize a command into a managed systemd service (auto-restart, at boot).
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.