Batocera Maintenance

Use when keeping a Batocera cabinet healthy over time: running scripts or scheduled jobs at boot and on an interval without cron, the custom_service boot-service pattern (which replaced custom.sh in v43), backing up /userdata to another machine over SSH, and upgrading between major Batocera versions (v42 to v43 and similar) including the ROM-directory renames and post-upgrade checklist. Covers why there is no crond, the backup-before-upgrade doctrine, and catch-up scheduling. Not for performance tuning (batocera-tuning).

t3chnaztea Updated
batocera-skills: agent skills for running a real arcade cabinet

File contents

t3chnaztea/batocera-skills commit 6d05646533

Frequently asked questions

npx get-skill add t3chnaztea/batocera-maintenance