Deploying Reaparr

Introduction

Reaparr is a library management and cleanup tool designed to work alongside the *arr stack (Sonarr, Radarr, Lidarr). It helps maintain your media library by automating cleanup tasks, managing disk space, and removing unwatched or unwanted content based on configurable rules.

Key features of Reaparr include:

• Automated Cleanup: Remove content based on age, watch status, or custom rules
• Multi-App Support: Works with Sonarr, Radarr, and Lidarr
• Disk Space Management: Free up space when storage runs low
• Watch Status Integration: Connect with Plex, Jellyfin, or Emby for watch tracking
• Dry Run Mode: Preview changes before execution
• Scheduling: Run cleanup on configurable schedules
• Web Interface: Monitor and manage cleanup operations
• Notifications: Alerts via Discord, Telegram, and more

This guide walks through deploying Reaparr on Klutch.sh using Docker and configuring library cleanup automation.

Prerequisites

Before deploying Reaparr on Klutch.sh, ensure you have:

• A Klutch.sh account
• A GitHub account with a repository for your Reaparr configuration
• Running instances of Sonarr, Radarr, or Lidarr
• API keys for your *arr applications
• Basic familiarity with Docker and media management

Deploying Reaparr on Klutch.sh

Create Your Dockerfile

Create a Dockerfile in your repository:

FROM ghcr.io/reaparr/reaparr:latest

# Environment configuration
ENV PUID=1000
ENV PGID=1000
ENV TZ=Etc/UTC

# Expose the web interface
EXPOSE 8080

# Volume for configuration
VOLUME /config

Push Your Repository to GitHub

Commit and push your Dockerfile to your GitHub repository.

Create a New Project on Klutch.sh

Navigate to the Klutch.sh dashboard and create a new project named “reaparr”.

Create a New App

Create a new app within your project and connect your GitHub repository.

Configure HTTP Traffic

In the deployment settings:

• Select HTTP as the traffic type
• Set the internal port to 8080

Set Environment Variables

Configure the following environment variables:

Variable	Value
PUID	1000
PGID	1000
TZ	Your timezone
SONARR_URL	URL to your Sonarr instance
SONARR_API_KEY	Your Sonarr API key
RADARR_URL	URL to your Radarr instance
RADARR_API_KEY	Your Radarr API key

Attach Persistent Volumes

Add persistent storage:

Mount Path	Recommended Size	Purpose
/config	1 GB	Configuration and logs

Deploy Your Application

Click Deploy to build and start your Reaparr instance.

Access Reaparr

Once deployment completes, access your Reaparr instance at https://your-app-name.klutch.sh.

Configuring Cleanup Rules

Basic Rules

Configure cleanup rules in the web interface:

1. Navigate to Settings > Rules
2. Create rules based on:
   • Content age (e.g., remove shows older than 1 year)
   • Watch status (e.g., remove watched content after 30 days)
   • Size (e.g., target specific file sizes)
   • Tags (e.g., exclude tagged content from cleanup)

Watch Status Integration

Connect to your media server for watch tracking:

1. Go to Settings > Integrations
2. Add your Plex, Jellyfin, or Emby connection
3. Configure user-specific watch status tracking
4. Rules can now use “watched” status

Dry Run Mode

Always test rules with dry run:

1. Enable dry run in Settings
2. Run the cleanup manually
3. Review proposed changes
4. Disable dry run when satisfied

Additional Resources

• Reaparr GitHub Repository
• Radarr Deployment Guide
• Klutch.sh Persistent Volumes

Conclusion

Deploying Reaparr on Klutch.sh provides automated library cleanup and management with automatic builds, persistent storage, and secure HTTPS access. Keep your media library organized and manage disk space efficiently with configurable cleanup rules.