← ClaudeAtlas

server-maintenancelisted

Set up or review routine maintenance on a self-hosted Docker box (Postgres backups, disk alerts, Docker cleanup, hardening).
simbaTmotsi/simba-skills · ★ 2 · DevOps & Infrastructure · score 78
Install: claude install-skill simbaTmotsi/simba-skills
# Server maintenance Routine care for a single self-hosted Linux host running Docker: scheduled Postgres backups, an hourly disk alert, weekly Docker cleanup, all installed via cron, plus a hardening review. Four generic scripts do the work, configured by environment variables (each documents its own at the top). They ship as Markdown in [scripts/](scripts/) (`pg-backup.sh.md` and so on) because the plugin directory does not accept executable files; step 2 extracts them. The full review lives in [references/docker-hardening-checklist.md](references/docker-hardening-checklist.md). Investigate before changing anything. Ask the user before every step marked **(ask)**. ## 1. Survey (read-only, run in parallel) ```bash df -h; docker system df docker ps --format '{{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}' crontab -l 2>/dev/null; ls /etc/cron.d 2>/dev/null systemctl list-timers --no-pager 2>/dev/null | head -20 docker version --format '{{.Server.Version}}' cat /etc/docker/daemon.json 2>/dev/null ``` Look for existing backup, alert or cleanup jobs before adding new ones. If something already covers a job, review it against the sections below instead of duplicating it. Report what exists, what is missing, and what looks wrong. ## 2. Choose an install location Agree with the user on a directory for the scripts (for example `~/server-maintenance`), a backup directory (`$BACKUP_DIR`) and a log directory. Prefer a backup location on a different disk from Docker's data; if th