From a fresh server to a panel-ready one, with proof.
server-prep locks down a new server (SSH keys on a new port, a firewall that also covers Docker, intrusion blocking, automatic security updates) and gets it ready for your deployment panel. An audit runs before and after, so you see what changed.
Pick your server and panel. See exactly what you get.
The dashboard, the firewall faceplate, the logins, the commands and the config file all follow your choices.
Your server after server-prep
If SSH locks you out: log in from the console. sudo ufw disable opens the firewall again. sudo bash /var/lib/server-prep/backups/<date>/rollback.sh restores every file server-prep changed. The 10-minute auto-undo only covers the SSH settings, not the firewall.
Your config file
Save it next to the scripts. It never holds secrets: tokens are typed at the prompt. Filled configs are ignored by git.
Two scripts, every step listed.
Each step can run twice safely, backs up the files it changes, and goes in the report. Use --only or --skip with these names. Switch optional steps here and the config above follows.
First boot server-preconfig.sh
Security server-prep.sh
server-audit.sh, read-only.
Checks per area
Each check counted once, by the worst result it can give
Same scripts. A few details change.
Let Claude Code walk you through it.
The repo ships project context and skills, so an agent can guide you question by question. You stay in control: you run every sudo command and type every secret yourself.
Claude Code + /new-server
/new-server: guided setup, from first SSH to the final audit./audit-review: paste an audit, get a fix for every WARN and FAIL./monitoring: Telegraf, InfluxDB and Grafana./add-step: the checklist for changing the scripts.- Codex finds the same skills: type
$new-server, or pick one from/skills.
For beginners
- A beginner mode that asks plain questions and stops before risky steps.
- JSON output from every script, so the agent reads facts.
- Openship support at the same level as Coolify.