How to Self-Host Automatic Ripping Machine
Automatic Ripping Machine headless automation for detecting inserted CDs, DVDs, and Blu-rays, then ripping, naming, transcoding, and organizing the result. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Automatic Ripping Machine is a good fit
Choose Automatic Ripping Machine when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Follow the project wiki for Docker or native Linux installation. The host must expose the optical drive and udev events to the service.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Separate temporary transcode space from the final media library, and back up only configuration plus irreplaceable output.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Ripping encrypted or copyrighted media is jurisdiction-dependent; use it only for media you are legally allowed to copy.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
