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. 01reconcurrent locale — already equal → nothing to do
2. 02reconis the locale already generated/installed?
3. 03reconDebian/Ubuntu (locale-gen) or RHEL/Fedora (glibc-langpack-xx)
4. 04actGenerate or install the localeverify
5. 05actSet ${locale} as defaultverify

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. 01verifyGenerate or install the localeVerified bylocale -a | grep -ci "^$(echo '${locale}' | cut -d. -f1)\.utf"
2. 02verifySet ${locale} as defaultVerified bylocalectl status | grep -c "LANG=${locale}"

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 Locale 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 system recipes

1. 01TimezoneSets the server timezone.
2. 02CockpitCockpit web administration console, local-only (SSH tunnel) by default, on :9090.
3. 03Zsh + Oh My ZshZsh with Oh My Zsh for the current user.
4. 04Synchronized clock (chrony)NTP synchronization via chrony.
5. 05User + sudoCreates a user with SSH key and sudo access. Destructive: system account.