techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.2K
active users

#radarr

0 posts0 participants0 posts today

My #Helm chart for a complete home media/streaming stack, Flex has been updated to version 0.2.0 🎉

Previously, it supports
#Plex as the streaming service, #Bazarr for automated subtitle downloads, #Flaresolverr for bypassing web protections/challenges, #Jackett as proxy server for #torrent trackers, #Overseerr as an interface for requesting media, #qBittorrent as the torrent client, #Radarr for downloading/managing movies, and #Sonarr for downloading/managing TV shows.

Now, to reduce reliance on Plex and lean towards a completely
#FOSS stack, I've added in support for #Jellyfin as a drop-in replacement for Plex, #JellyPlex-Watched for syncing watch states between Jellyfin/Plex servers, and #Jellyseerr as a drop-in replacement for Overseerr, which not only works with Plex but also Jellyfin.

I've been using this for over a year at this point and it works perfectly. For me personally, I have everything supported deployed using this on my
#Kubernetes cluster except for Jellyfin, Plex, and qBittorrent, which I've deployed as individual VMs instead on #Proxmox cos I find it less resource/bandwidth taxing on my cluster that way - this shouldn't be an issue if your cluster is a lot beefier. During non-peak loads, the (Flex) stack uses up a total of only ~0.19 CPU core and ~1.6GB memory.

🔗 https://github.com/irfanhakim-as/charts/pull/136

Changes

Updated chart to match current base template
Added support for modularity for all containers - pick and choose what you need/don't
Made improvements to various var assignments and cond...
GitHubflex: General update by irfanhakim-as · Pull Request #136 · irfanhakim-as/chartsBy irfanhakim-as

#ayuda fediverso #sonarr
recien hice un rebuild de mi raspberry, y he vuelto a montar el stack #sonarr #radarr #lidarr #prowlarr y #torrent
con sonarr, me pasa algo que no me pasa con los demas. y tienen la misma configuracion?
"download client unavailable" cuando busca contenido
pero sin embargo, desde sonarr, y prowlarr, el cliente me da OK cuando lo testeo (deluge)
tengo todos los contenedores pasando por #tailscale
Este es mi stack de sonarr:
---
version: "3.7"
services:
ts-sonarr:
image: tailscale/tailscale:latest
container_name: ts-sonarr
hostname: sonarr
environment:
- TS_AUTHKEY=${KEY}
- TS_SERVE_CONFIG=/config/sonarr.json
- TS_STATE_DIR=/var/lib/tailscale
- TS_HOSTNAME=sonarr
volumes:
- ${WD}/ts-sonarr/state:/var/lib/tailscale
- ${WD}/ts-sonarr/config:/config
devices:
- /dev/net/tun:/dev/net/tun
cap_add:
- net_admin
- sys_module
restart: unless-stopped
sonarr:
env_file: stack.env
image: lscr.io/linuxserver/sonarr:latest
container_name: sonarr
environment:
- PUID=1000
- PGID=1000
- UMASK=002
- TZ=Europe/Madrid
volumes:
- ${WD}:/config
- ${MF}:/mnt/nas/data
restart: unless-stopped
network_mode: service:ts-sonarr
volumes:
sonarr-data:
driver: local
ts-sonarr:
driver: local
@sancas @matiargs @sam
se agradece #boost

#Cross-Seed has released its long-awaited v6.

My advice - get the config.template.cjs and edit that with your data. Much easier than editing your current template.
Carefully read breaking changes: cross-seed.org/docs/v6-migrati
Also - configure #Sonarr and/or #Radarr api for better media detection (cross-seed.org/docs/tutorials/).
Also, also enable flatLinking if you use an external manager like #qbit_manage (cross-seed.org/docs/v6-migrati).

github.com/cross-seed/cross-se

Well, added a storage tier this evening.

A couple 4 Tb drives which I had laying about, as #JBOD (#MergerFS), for those media files which are "replaceable" and don't really need to be on #ZFS mirrors (~70 & ~16 Tb).

I now feed into #Plex from the different tiers using #OverlayFS.

Pretty neat. I can move things around without Plex noticing, select the tier in #Sonarr / #Radarr, and if one of those 4 Tb drives goes down, NBD and I can see what is missing.

More iops don't hurt either.

#ayuda fediverso
Cual es la mejor forma de generar / usar #certificados #ssl en contenedores locales de #docker ? Es para #radarr #sonarr #plex etc...
Las opciones que impliquen #letsencrypt no las veo posibles porque estoy dentro de #cgnat y estoy ahora mismo atascado con la opción de #cloudflare tunnels (véase este hilo tkz.one/@audricd/1131979542609) y letsencrypt funciona exclusivamente si le puedes apuntar un dominio accesible desde Internet, si lo he entendido correctamente? #cerbot tengo entendido que es la alternativa local? Cuales son las mejores prácticas, que debería de tener en cuenta? Alguna guía que compartir?
Se agradece boost

TKZ.OneAudric (@audricd@tkz.one)Adjunto: 3 imágenes #ayuda #cloudflare @elsultan77@fe.disroot.org @pijusmagnificus@gotosocial.gundan.es estoy tratando de establecer un tunel cloudflare, ya que soy un pringado detras de cgnat, pero el dominio no me resuelve un nginx que tengo en la raspberry puerto 8089 (que es un hello world, de prueba)

#ayuda fediverso
para un plexbox accesible desde internet, que opcion recomiendas?
quiero poder usar y manejar #sonarr #radarr #lidarr #prowlarr #plex, y otros servicios tipicos de #selfhosting como #web, #git en una #raspberry acoplada a un #nas, desde el exterior, con seguridad. y hacer las tipicas trastadas, experimentos de selfhosting. pero estoy limitado a soluciones para #arm (rpi5)

se agradece boost
@asturel
@zicoxy3
@ximo
@sancas

Our friendly neighborhood movie pirates do a lot of things right when they encode a movie and make it available.

Correctly including & flagging forced subtitles is too-often not one of those things.

It takes a few minutes, but I'm getting pretty-okay at fixing some of those issues with MKVToolnix. (unflagging the wrong subs as forced, flagging the right ones as forced, removing not-English forced subs so Jellyfin doesn't try to show them)

#radarr#bazarr#plex

Apparently #SnapRAID syncs are supposed to be fast.

#Radarr & #Sonarr update my media timestamps with the original airdate on every rescan.

In doing so, a time with an exact-zero nanoseconds is used. SnapRAID hates this, and nudges you to use `snapraid touch` to apply a random nonzero nanosecond value to the timestamp.

Then Sonarr/Radarr comes back and resets the nanoseconds to 0.

Turns out my 2-hour SnapRAID syncs finish in just a few seconds if the timestamps don't keep changing. #homelab

Continued thread

Apparently I'm an idiot, and I'm glad I popped into the *arr Discord to ask. , , , and others have a option that's a bit more setup but works.

In my defense, in all of my searching for a solution to *arr using SQLite on Docker Swarm not once did I come across any indication that they had support for another DB. In fact, it seems like I came across indication that the opposite was true.

Regardless I have a project now for after we get back from camping this week. And with any luck, I'll finally stop losing my mind with DB corruption issues and have a more robust setup.

Continued thread

I think would work well for folks who want to keep up with current artists and grab their latest releases. My music tastes are for older artists who aren't releasing anymore. Aside from the nice GUI for grabbing torrents from various trackers, I don't really need it to download music or to sort it - does an awesome job keeping my music library sorted and up-to-date.

is the one I definitely need to keep, I grab some kids shows with that. can be replaced or removed - it's nice to keep up with movie series and download recent releases in those series, but otherwise I can just find movies myself.

Looks like I will need to research a replacement for Lidarr. Dunno why I felt committed to making it work when it refuses to play nice on swarms.

I think I have one other service that uses SQLite on my swarm, but I don't use it nearly as much and I haven't seen it throw problems like *arr does.

Continued thread

After a few months, I've migrated everything to my cluster, removed the old MacBook, even got 2 versions of running and a couple other fun services.

The problem is even though was the right choice in the moment, *arr apps absolutely HATE network storage. is the culprit, and the devs for , , , and others appear completely uninterested in switching away from SQLite. I would prefer , but evidently, even though this issue repeatedly comes up, folks like me who want to run *arr apps on a swarm are edge cases.

So, I could restrict each app to a specific node, which I don't want to do because a couple of my nodes will randomly stop working and require me to manually restart them. Or, I can continue to put up with DB corruption, which is proving to be a real pain.

Or search for another solution to replace *arr? Truth be told, I use Lidarr the most and it isn't super great at what it does.