heroeswearkapes/tdarr_server repository overview

⁠Deprecated

This image is no longer actively maintained.

tdarr_server was originally created as a customized version of the official Tdarr Server to support a specific AV1-focused workflow and provide additional startup safeguards.

The custom image included functionality such as:

• Tdarr database integrity checks during startup
• Automatic database recovery from available Tdarr backups
• AV1-oriented library configuration normalization
• Additional utilities used by the recovery process

The original workflow that required these customizations has since changed, and current Tdarr releases have significantly improved their built-in media and AV1 support.

Rather than continue maintaining a separate Tdarr Server image, new installations should use the official Tdarr Server image:

ghcr.io/haveagitgat/tdarr:latest

⁠Existing Users

Existing versions of this image will remain available and are not being removed.

Existing deployments can continue using their current image, but no further updates are planned.

Users are encouraged to migrate to the official Tdarr Server image when convenient:

ghcr.io/haveagitgat/tdarr:latest

Before migrating, make sure your existing Tdarr configuration and database are backed up.

⁠Database Recovery Functionality

One useful part of this custom image was its additional database integrity and recovery logic.

Rather than continue maintaining an entire custom Tdarr Server image solely for this functionality, the remaining database-related behavior will be investigated against the current upstream Tdarr project.

Where appropriate, improvements may be proposed directly to Tdarr so they can benefit the wider community without requiring a separate server image.

⁠Why This Image Was Deprecated

Maintaining a complete custom Tdarr Server image creates additional complexity and can cause custom behavior to diverge from upstream Tdarr.

Some behavior in this image also automatically modified Tdarr library configuration to support the original AV1 workflow. That behavior is no longer appropriate as a general-purpose default.

Using the official image provides:

• Direct upstream Tdarr updates
• Current Tdarr functionality
• Fewer custom modifications
• Simpler troubleshooting
• A clearer upgrade path

The remaining useful custom functionality is better evaluated as a potential upstream contribution rather than maintained indefinitely as a separate Docker image.

⁠Official Tdarr Server

New installations should use:

ghcr.io/haveagitgat/tdarr:latest

For Tdarr documentation and current installation instructions, refer to the official Tdarr project.

⁠Thank You

Thanks to everyone who used this image while these additional safeguards and AV1-specific customizations were useful.

The existing image and tags will remain available for users who still depend on them.