I need testers for this fork of readarr, if anyone is interested in let me know if you have any issues.

https://github.com/Rorqualx/Librarr

SSO is not enough if your media services are still exposed directly.

ArrGate is a Go CLI that discovers risky Docker Compose exposure, verifies proxy-only access, applies transactional network isolation, and leaves operator-readable recovery metadata behind.

Built for self-hosted Sonarr, Radarr, Prowlarr, Lidarr, Readarr, and Caddy/Authentik-style stacks.

• Detect published service ports
• Gate changes with preflight checks
• Reconcile Compose networking transactionally
• Verify no-bypass access paths
• Track recovery and rollback state
• Run a Go test, race, lint, and compatibility matrix in CI
• https://github.com/NolanCotter/ArrGate

bonjour! j'utilise la suite ARR depuis ses début (un peu plus de 15ans) et la famille c'est beaucoup agrandis! j'ai longtemps fait avec un Favoris pour chaque ARR, puis il y a eu Lunasea, Helamarr,... mais a chaque fois j'avais toujours besoin de mes vieux favoris. j'ai donc fait ce que je recherchais, un dashboard (et des widgets) pour avoir directement les infos importantes, une recherche de medias unifié (si c'est dans ma médiathèque ça l'affiche, si ça n'y ai pas ça créer une demande seerr, si je veux juste faire un suivis de la serie que je regarde sur un services de streaming ça le fait aussi) ça affiche ma bibliothèque et bon nombres de fonctions des ARR, ça gère les torrents, il ya un suivis des DLs a travers les ARR (demande, grab, import, disponibilité). je peux garder un oeil sur mes stockages, le fonctionnement de mes container docker... et plein de choses a venir j'espère ;)

pour le moment j'ai 8 services d'intégrés:

-Seerr

-Sonarr

-Radarr

-Prowlarr

-QBittorrent

-QuiV2

-Portainer

-Jellyfin

http://www.lumiarr.eu (c'est des captures de ma V1 il y peu des évolutions depuis)

Édit: pour le moment les 10 places ne sont plus disponibles j'en remettrais d'ici peu ;)

Pour ceux que ça intéresse https://testflight.apple.com/join/j7JtuAxb il y a 10 places.

I'm wondering if there is anything that will help with managing multiple sonarr and radarr instances (I've now got 8... 4K, Regular, Anime, and Kids). I'm using Profilarr 2.0 and that does a lot of the heavy lifting, but if anyone's got anything else to suggest, that would be worth checking out, please suggest it.

Every time Sonarr renames a file, qBittorrent loses it and stops seeding. I know the hardlink workaround, but it breaks the moment your downloads and media are on different volumes.

So I spent a few weekends building arr-sync — a daemon that watches your media folders and automatically resyncs qBittorrent when a file moves or gets renamed. Matching is done via BitTorrent piece hashes, not filenames, so it actually works.

Wrote it in Gleam mostly because I wanted to learn it, and honestly the OTP supervision tree was perfect for this kind of long-running process. Had to write a couple Erlang FFI shims for the filesystem watcher and the piece hasher but nothing crazy.

Still some rough edges (pure v2 BitTorrent torrents can't be matched, qBittorrent bug), documented in the README.

https://github.com/Chahine-tech/daemon

Happy to answer questions, especially around the Gleam/OTP bits since that was the most interesting part to figure out.

EDIT: a few days later we have V1.11.0 available. A bunch of fixes to issues reported by people here and on GitHub and several new improvements. Check out the full changelog here.

It's Friday, Digarr just passed 100 stars on GitHub, and v1.10.0 is out. That's the first stable 1.x line, so it felt like a good moment to share it properly.

Digarr is a self-hosted music discovery layer that sits in front of Lidarr (or your media server). It learns what you listen to, asks an AI provider for new artists and albums, scores them, and hands you a review queue. You approve what you like and it goes to Lidarr or a playlist target. The data stays on your server.

A few things I think it does well:

• An AI taste pipeline you actually control. It builds a profile from your listening sources, asks your AI provider for candidates, then scores them with weights you set (consensus, similarity, genre overlap, AI confidence, popularity, and learning from your past approvals). You pick the provider: Anthropic, OpenAI, Gemini, Ollama, or any OpenAI-compatible endpoint. Point it at Ollama on localhost and nothing leaves your box.
• Album-level discovery. Most tools only recommend artists. Digarr also finds individual albums: studio albums you are missing from artists you already follow, new releases you missed, and net-new finds from artists you don't have yet. Approving an album adds the artist to Lidarr unmonitored and grabs only that album, so you don't pull a whole discography to get one record. As far as I can tell, nothing else in this space does album-level discovery.
• Mood discovery. Type "something like Boards of Canada but darker" or "upbeat 90s pop for a road trip" and it turns that into a result set. No filter-building first.
• Works with or without Lidarr. If you don't run Lidarr, discovery-only mode still works and pulls from ListenBrainz, Last.fm, Spotify, Deezer, Plex, Jellyfin, Emby, and Discogs.

The basics, in short:

• Connects to Lidarr, Plex, Jellyfin, Emby, and slskd, plus ListenBrainz, Last.fm, Spotify, Deezer, and Discogs
• Review queue with approve / reject / skip, swipe on mobile, card stack on desktop
• Discovery modes (Artist Radio, Release Radar, Library Gap-Fill, Charts, Deezer Flow, Spotify Saved Albums, and more) you can run on demand or schedule as subscriptions
• Auto-playlists to Navidrome, Jellyfin, Emby, Plex, or Spotify, or export as M3U / XSPF
• Genre browser, decade filter, cross-platform search, 30-second previews
• Multi-user with OIDC/SSO and per-user sources, weights, and targets
• Backup and restore, job history, webhook notifications (Discord, Slack, ntfy, Gotify) with an optional scheduled digest
• 15 UI languages with locale-aware AI output, 15 color themes in dark and light
• One container that runs next to your existing stack. Free and open source, MIT.

On the AI question, since it always comes up: this is built with AI assistance, and I drive it. I set the roadmap, design the architecture and the UX, decide which features ship, and review every change. The AI writes most of the code and tests under that direction. I'd rather say that up front than have someone find it in the commit history.

GitHub: https://github.com/iuliandita/digarr

Happy to answer questions, and bug reports or feature ideas are welcome in the issues.

I made a music requesting service for use with Lidarr. Docker backend with a web or android app UI. On GitHub. Works best with soularr and slskd.

Since Sonarr cannot work with One Pace (fan edits), I built a tool to

• verify existing collection
• reorganize existing collection
• update metadata of existing collection
• monitor new releases
• download new releases through torrent (qBittorrent and Deluge)
• import new releases
• add metadata (and poster art) on Plex/Jellyfin/Emby

There are tools around that do SOME of this, but none yet that does ALL and none that you can just deploy in your stack and it just works like it's supposed to...

You can read all about it in the github page:
https://github.com/eltharynd/OnePacerr

Sorry if this is kind of a repost tbh, I posted this not long ago...
However I know how difficult it is to find stuff on reddit and I know I searched for a tool like these for days before I decided to develop my own.

UPDATE: Currently it supports Plex, Emby, Jellyfin, just a local folder without any media server (also creates the NFO files if you want to import them at a later time).

As well as qBittorrent, Deluge, Transmission and uTorrent.

I also created my own One Pace metadata API and make it available to the public https://github.com/eltharynd/one-pace-api

This allowed me first of all to scan/scrape more often due offloading the taste to the backend itself, so that not every install has to do it potentially clogging servers I don't own, and, most importantly, to create a WebSocket so that I can notify clients about metadata updates or new episode releases.

In short, it receives a notification whenever something changes and is able to download/organize the new episodes automatically for you without the need to periodically check for new updates on its own.

If I can say so myself, it shaped up to be a really good tool. If you watch One Pace, and especially if you do so via a media server, I highly recommend you check it out. I promise you won't regret it :)

I have been busy with life recently so I did not have the chance to work on my side project but here we are again.

Bazarr-sync v0.7

its a cli tool that solve a problem in bazarr. syncing multiple different subs has always been a chore. especially when you reach the level of hoarding hundreds of movies and shows . this tool aim to make it a little bit easier.

latest update wad almost 1 year ago . I fixed many of the issue and bugs here and there. so it should fly smoothly.

and yeah there is a docker container as well.

what's new - sync subtitles of a certain language. - improve terminal compatibility - fixed a leak in Http requests causing crashes - resume inturrepted syncs

Disclaimer:

the original code was completely written by hand. this update includes some vibe coded elements. but reviewed .

https://github.com/ajmandourah/bazarr-sync

Heyo..
So I'm a One Pace watcher and getting all their episodes in plex has been kind of a bother so far...

Since they now have an RSS feed for new episodes I built this tool you can deploy in your Home Lab to automatically download all episodes through qbittorrent, copy/rename them in plex folder, trigger plex folder scan and update metadata.

It's the tool I wish I had... I used to have to manually handle most of it (there are some helper tools but none fully automated) but now you can just set it up and it can download the episodes you're missing (even checking the hash if you want) and will continue to monitor for new releases.

Hope it's useful
https://github.com/eltharynd/OnePacerr

The donkey is back!!

After five years of silence, aMule has received a new release with dramatic download speed improvements, have a look at the release notes: https://amule-org.github.io/changelog/3.0.0

Mularr now is updated and includes aMule v3.0.0 making this tool even more powerful, if you haven't tried it yet:

https://github.com/joecarl/mularr

It feels like every day we get new apps posted that are pretty clearly AI coded. As a group how do we feel about AI generated projects? Do we allow them? What about security concerns?

I'm not a programmer so I don't have the skills needed to dig into the code to check these projects.

Hello,

I have been trying to use Lidarr for awhile now but did not like the way it handled the process. It worked but it didn't feel like it was good for me.

I have created a new arr called Echoarr that is fully open sourced.

I have created Echoarr so it works with torrents and soulseek and gives more control over the music.

I am still adding many more features. I need the help of fellow Redditors to figure what features are requested or need fixing.

This is my first big project to create and uploading to GitHub

Please let me know. Thank you

[GitHub](https://github.com/Deraga07/Echoarr/tree/main)

Sorry for describing without copy-pasted error messages: this was a problem I had inside a headless VM on a somewhat physically inaccessible server.

For the first time in about 6 months I updated hotio's versions of radarr, sonarr, lidarr, bazarr, prowlarr, jackett, sabnzbd. And they all stopped working. The logs output was very long but boiled down to "no write access to /config"

That would normally be the .yml and POSIX. But the file permissions on mapped directories were all still correct and the users were still all in their correct groups, so docker run was able to write and delete files inside the container with no difficulties. Lots of minor amends were attempted to docker-compose.yml for hours, and pretty much everything was rebuilt. But then switching from hotio to linuxserver brought everything back up with no further changes.

I cannot at all debug now. And there is no Issues section on hotio's Github. Or installation/dependencies documentation for that matter 😞 But I wonder if maybe there was some security update of hotio's Alpine that somehow relies on systemd for dropping from root to UID:1000?

Has anyone else also seen this?

Anyone have any luck with getting BigFinish Audio dramas on Readarr? Just interested in knowing before I commit to adding this to my stack

Cheers

Edit: BTW, I want to thank everyone for the support over the past weeks since alpha4 dropped. We went from 1,790 to 64,200(!) downloads in just four weeks. Thank you! It is definitely motivating to keep pushing hard. Hopefully everyone will like the new release. I think we'll probably do one more alpha release (alpha6) sometime in June, then move to an extended beta throughout the summer months.

Hi everyone -

Livrarr is an AI-generated Readarr replacement. Single instance supports ebooks and audiobooks. Rust / React for efficiency and speed. Still in alpha - please expect rough edges.

After about 4 weeks of development, alpha5 just dropped with some new features:

Metadata & search

• Google Books integration — primary source for foreign-language books, fallback for English
• Audible catalog provider — ASIN + title/author lookup for audiobook metadata and covers
• Goodreads LLM-assisted lookups (when ISBN search misses)
• CJK title matching (Japanese/Chinese/Korean)
• OpenLibrary policy-compliant User-Agent (no more silent 403s)

Covers

• Audiobook covers now auto-populate (Audnexus + Audible)
• Multi-cover trust system — user picks are locked, auto-enrichment only swaps when better
• Cover picker UI — browse alternatives across all providers, one click to swap
• Media-aware priority — audiobook covers prefer Audible/Audnexus; ebook covers prefer Hardcover/OL
• ISBN→OL→Amazon fallback chain for cover acquisition

Reading & listening

• Chapters, bookmarks, and position memory in both the EPUB reader and audiobook player
• Progress carries across sessions and devices
• EPUB reader: right-arrow now properly advances past the cover page

Imports & delivery

• CSV imports from Goodreads and Hardcover library exports
• Manual import scan — point at a folder, auto-classify and match
• Readarr import for existing libraries
• Send to Kindle via SMTP (Gmail/Outlook presets or custom)

Indexers & download clients

• Transmission support added
• qBittorrent fixes (server-side .torrent fetch, body-content check)
• Server-side media-type filtering (no more client-side bugs)

UI

• First-run onboarding wizard
• System status page (provider health, queue depth, indicators in sidebar)
• Series collapse on poster page
• Language filter on works page
• Overview density: series, rating, page count, duration, narrator, genre badges
• Recently-downloaded sort

Reliability

• PID file deadlock on container restart fixed (was causing 502s on restart)
• Live metadata config reload (provider keys + LLM settings without restart)
• Gemini model name auto-migration
• Multi-arch Docker images (native amd64 + arm64) — thanks to community contributor u/eskimoprince

Previous Functionality:

• Foreign language support (requires free LLM API key) - definitely need testers on this - I tried my best, but I don't read books in Spanish / German / French / Polish, etc.
• Series monitoring
• Readarr library import (experimental, but will NOT touch your files)
• Prowlarr integration
• Mail-to-Kindle support
• Media consumption: EPUB and audiobook player; OPDS catalog
• Mobile friendly UI
• And other assorted odds and ends

Links:

• GitHub: https://github.com/kkodecs/livrarr
• Docker: docker pull ghcr.io/kkodecs/livrarr:0.1.0-alpha5
• Issues: https://github.com/kkodecs/livrarr/issues
• Discord (updated): https://discord.gg/PJDsgjEvCV

Additional information:

• AI generated. Claude Opus 4.6/4.7 with Gemini 3.1/3.5 and GPT 4.5/5.5 cross-family adversarial review on everything.
• Extensive automated testing including fmt, clippy, backend tests, frontend linting, tsc strictmode, vitests, etc.

Feedback appreciated - thank you!