#overseerr β Public Fediverse posts
Live and recent posts from across the Fediverse tagged #overseerr, aggregated by home.social.
-
@yehor In addition to request management, one very good reason to use #Overseerr is content discoverability. Just opening up the homepage and browsing the trending list can give you some insight into what is hot at the moment
-
I installed the #Plex app on my brother's TV during my last visit to his place. Created an account for them and shared my library. They were sceptical.
Now they are using it regularly and are requesting new movies =) I'm happy and thinking about an #Overseerr
-
This is some good news!
I've been using #Overseerr for some time now, and its development has been ... lacking. -
@[email protected] Nice. So essentially this is sort of #overseerr meets #tautulli kinda platform?
-
Ever since moving from #Plex to #Jellyfin months ago, I've also moved from #Overseerr to #Jellyseerr. I'm looking to deploy #Lidarr at some point, so it's nice to see that Jellyseerr already has a PR ready to incorporate Lidarr support - Overseerr had one too previously, but it's unfortunately been scrapped.
π https://github.com/fallenbagel/jellyseerr/pull/1238
π https://github.com/sct/overseerr/pull/3800 -
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 -
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 -
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 -
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 -
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 -
Everything that's currently cooking with my "Flex" everything-you-need-in-a-home-media-server #Helm chart: #Jellyfin support as an alternative to #Plex, #JellyPlex-Watched support to sync watch states between Jellyfin and Plex (also supports #Emby, but no plans to support it for now in my chart), and #Jellyseerr support as alternative to #Overseerr that also supports Jellyfin rather than just Plex. I'll update here once I've published it.
Ngl that "Flex" name is kinda (no, very) cringe, and it's clearly "inspired" by the name, Plex - I'm tempted to rename it to another cringey, mediocre name... but idk if it's worth the hassle haha. Also I'm lazy and don't have the skill to create a new logo for it. -
Everything that's currently cooking with my "Flex" everything-you-need-in-a-home-media-server #Helm chart: #Jellyfin support as an alternative to #Plex, #JellyPlex-Watched support to sync watch states between Jellyfin and Plex (also supports #Emby, but no plans to support it for now in my chart), and #Jellyseerr support as alternative to #Overseerr that also supports Jellyfin rather than just Plex. I'll update here once I've published it.
Ngl that "Flex" name is kinda (no, very) cringe, and it's clearly "inspired" by the name, Plex - I'm tempted to rename it to another cringey, mediocre name... but idk if it's worth the hassle haha. Also I'm lazy and don't have the skill to create a new logo for it. -
Everything that's currently cooking with my "Flex" everything-you-need-in-a-home-media-server #Helm chart: #Jellyfin support as an alternative to #Plex, #JellyPlex-Watched support to sync watch states between Jellyfin and Plex (also supports #Emby, but no plans to support it for now in my chart), and #Jellyseerr support as alternative to #Overseerr that also supports Jellyfin rather than just Plex. I'll update here once I've published it.
Ngl that "Flex" name is kinda (no, very) cringe, and it's clearly "inspired" by the name, Plex - I'm tempted to rename it to another cringey, mediocre name... but idk if it's worth the hassle haha. Also I'm lazy and don't have the skill to create a new logo for it. -
Everything that's currently cooking with my "Flex" everything-you-need-in-a-home-media-server #Helm chart: #Jellyfin support as an alternative to #Plex, #JellyPlex-Watched support to sync watch states between Jellyfin and Plex (also supports #Emby, but no plans to support it for now in my chart), and #Jellyseerr support as alternative to #Overseerr that also supports Jellyfin rather than just Plex. I'll update here once I've published it.
Ngl that "Flex" name is kinda (no, very) cringe, and it's clearly "inspired" by the name, Plex - I'm tempted to rename it to another cringey, mediocre name... but idk if it's worth the hassle haha. Also I'm lazy and don't have the skill to create a new logo for it. -
Everything that's currently cooking with my "Flex" everything-you-need-in-a-home-media-server #Helm chart: #Jellyfin support as an alternative to #Plex, #JellyPlex-Watched support to sync watch states between Jellyfin and Plex (also supports #Emby, but no plans to support it for now in my chart), and #Jellyseerr support as alternative to #Overseerr that also supports Jellyfin rather than just Plex. I'll update here once I've published it.
Ngl that "Flex" name is kinda (no, very) cringe, and it's clearly "inspired" by the name, Plex - I'm tempted to rename it to another cringey, mediocre name... but idk if it's worth the hassle haha. Also I'm lazy and don't have the skill to create a new logo for it. -
Finally starting to make the transition over from #overseerr to #jellyseerr. Overseerr just hasn't been updated in like a year or more. The hell is up with that!
They are probably just looking at the box every half an hour like I am ( look at my previous post )
#homelab #selfhosted #selfhosting -
Why did it take me so long for me to finally use #sonarr, #overseerr, #radarr, #prowlarr, and #readarr because it's so much more convenient to have seasons automatically download instead of remembering to manually download them.
-
Why did it take me so long for me to finally use #sonarr, #overseerr, #radarr, #prowlarr, and #readarr because it's so much more convenient to have seasons automatically download instead of remembering to manually download them.
-
Why did it take me so long for me to finally use #sonarr, #overseerr, #radarr, #prowlarr, and #readarr because it's so much more convenient to have seasons automatically download instead of remembering to manually download them.
-
Why did it take me so long for me to finally use #sonarr, #overseerr, #radarr, #prowlarr, and #readarr because it's so much more convenient to have seasons automatically download instead of remembering to manually download them.
-
When you setup a request channel on the #Plex you share with your family, you eventually get *some stuff* on there.
-
Having #Sonarr/#Radarr running for my #Plex setup has been such a gaaaaaaamechanger π© Like I don't need to have a .txt/.md file to keep track of what series I wanna add or in the process of adding, and go to #TVDB to check if a new episode/season is out, go look for them on #torrent sites, etc.
I literally just get on my #Overseerr server, request for a show/movie, and Sonarr/Radarr would just track them for me. Anytime a new episode/release is out, boom it's already been downloaded and added to my Plex server ready to watch. Should've done this a LONG time ago. -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
π #Plex: The media streaming frontend.
π #Jackett: The intermediary between these services.
π #FlareSolverr (opt): Jackett's helper for circumstances that require it.
π #qBittorrent (opt): #Torrent client.
π #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
π #Radarr: Media management tool for movies.
π #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
π https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
π #Plex: The media streaming frontend.
π #Jackett: The intermediary between these services.
π #FlareSolverr (opt): Jackett's helper for circumstances that require it.
π #qBittorrent (opt): #Torrent client.
π #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
π #Radarr: Media management tool for movies.
π #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
π https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
π #Plex: The media streaming frontend.
π #Jackett: The intermediary between these services.
π #FlareSolverr (opt): Jackett's helper for circumstances that require it.
π #qBittorrent (opt): #Torrent client.
π #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
π #Radarr: Media management tool for movies.
π #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
π https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
π #Plex: The media streaming frontend.
π #Jackett: The intermediary between these services.
π #FlareSolverr (opt): Jackett's helper for circumstances that require it.
π #qBittorrent (opt): #Torrent client.
π #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
π #Radarr: Media management tool for movies.
π #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
π https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Took me a long while but I've finally published my creatively named #Helm chart, #Flex (christ, save us devs) which is a collection of curated services that aims to provide a complete home media server solution in a neat, Helm package.
With this single package, you can deploy to your #Kubernetes (#RKE2) cluster:
π #Plex: The media streaming frontend.
π #Jackett: The intermediary between these services.
π #FlareSolverr (opt): Jackett's helper for circumstances that require it.
π #qBittorrent (opt): #Torrent client.
π #Overseerr: Media discovery/management tool/interface that connects to Plex, Radarr, and Sonarr underneath.
π #Radarr: Media management tool for movies.
π #Sonarr: Media management tool for TV shows/#anime.
This chart supports "local" storages such as #Longhorn, as well as #SMB shares - which I would recommend for the media side of things. This chart also supports, and recommends the use of #Ingress to get these services online.
It's very new so I'm sure there are a bunch of things missing that I could add/improve upon, but the current iteration has been tested pretty thoroughly on my own cluster, and I've done my best to ensure that the documentation (README) and values file are helpful (or try to be) at least.
π https://github.com/irfanhakim-as/charts/tree/master/mika/flex -
Finally overcame this
The slowdowns and weird behaviours were solved instantly simply by using PVCs with access mode: RWO rather than RWX - dk why this is the case, but it is so that's nice!
Everything works now, including: #Plex, #Jackett, #Radarr, #Sonarr, #qBittorrent, and #Overseerr. With this setup, all is needed to add a show to the media streaming frontend (will prolly explore the possibility of using #Jellyfin in place of Plex in the future) is to open up Overseerr and request for a movie/TV show - it will then contact Radarr/Sonarr to download said media using qBittorrent, after which the show will be picked up automatically by Plex.
The only "issue" left is that I notice the downloads either download slowly (hundreds of KiB/s on average), or sometimes even stall or be stuck at "downloading metadata" - even when it seems that the seeding ratio is pretty good. Dk if this is a "#Torrent" issue, or internet in a containerised environment issue (since internet speeds are fine on the host, and my own machine).
Don't really care abt said issue yet tho for now, just excited to be done with this #Helm chart as a "0.1.0" release, then improve on it further such as allowing the use of existing PVCs, external servers for each service (i.e. external qBittorrent server), etc.
RE: https://sakurajima.social/notes/9pk70gb36b -
Finally overcame this
The slowdowns and weird behaviours were solved instantly simply by using PVCs with access mode: RWO rather than RWX - dk why this is the case, but it is so that's nice!
Everything works now, including: #Plex, #Jackett, #Radarr, #Sonarr, #qBittorrent, and #Overseerr. With this setup, all is needed to add a show to the media streaming frontend (will prolly explore the possibility of using #Jellyfin in place of Plex in the future) is to open up Overseerr and request for a movie/TV show - it will then contact Radarr/Sonarr to download said media using qBittorrent, after which the show will be picked up automatically by Plex.
The only "issue" left is that I notice the downloads either download slowly (hundreds of KiB/s on average), or sometimes even stall or be stuck at "downloading metadata" - even when it seems that the seeding ratio is pretty good. Dk if this is a "#Torrent" issue, or internet in a containerised environment issue (since internet speeds are fine on the host, and my own machine).
Don't really care abt said issue yet tho for now, just excited to be done with this #Helm chart as a "0.1.0" release, then improve on it further such as allowing the use of existing PVCs, external servers for each service (i.e. external qBittorrent server), etc.
RE: https://sakurajima.social/notes/9pk70gb36b -
Finally overcame this
The slowdowns and weird behaviours were solved instantly simply by using PVCs with access mode: RWO rather than RWX - dk why this is the case, but it is so that's nice!
Everything works now, including: #Plex, #Jackett, #Radarr, #Sonarr, #qBittorrent, and #Overseerr. With this setup, all is needed to add a show to the media streaming frontend (will prolly explore the possibility of using #Jellyfin in place of Plex in the future) is to open up Overseerr and request for a movie/TV show - it will then contact Radarr/Sonarr to download said media using qBittorrent, after which the show will be picked up automatically by Plex.
The only "issue" left is that I notice the downloads either download slowly (hundreds of KiB/s on average), or sometimes even stall or be stuck at "downloading metadata" - even when it seems that the seeding ratio is pretty good. Dk if this is a "#Torrent" issue, or internet in a containerised environment issue (since internet speeds are fine on the host, and my own machine).
Don't really care abt said issue yet tho for now, just excited to be done with this #Helm chart as a "0.1.0" release, then improve on it further such as allowing the use of existing PVCs, external servers for each service (i.e. external qBittorrent server), etc.
RE: https://sakurajima.social/notes/9pk70gb36b -
Finally overcame this
The slowdowns and weird behaviours were solved instantly simply by using PVCs with access mode: RWO rather than RWX - dk why this is the case, but it is so that's nice!
Everything works now, including: #Plex, #Jackett, #Radarr, #Sonarr, #qBittorrent, and #Overseerr. With this setup, all is needed to add a show to the media streaming frontend (will prolly explore the possibility of using #Jellyfin in place of Plex in the future) is to open up Overseerr and request for a movie/TV show - it will then contact Radarr/Sonarr to download said media using qBittorrent, after which the show will be picked up automatically by Plex.
The only "issue" left is that I notice the downloads either download slowly (hundreds of KiB/s on average), or sometimes even stall or be stuck at "downloading metadata" - even when it seems that the seeding ratio is pretty good. Dk if this is a "#Torrent" issue, or internet in a containerised environment issue (since internet speeds are fine on the host, and my own machine).
Don't really care abt said issue yet tho for now, just excited to be done with this #Helm chart as a "0.1.0" release, then improve on it further such as allowing the use of existing PVCs, external servers for each service (i.e. external qBittorrent server), etc.
RE: https://sakurajima.social/notes/9pk70gb36b -
Finally overcame this
The slowdowns and weird behaviours were solved instantly simply by using PVCs with access mode: RWO rather than RWX - dk why this is the case, but it is so that's nice!
Everything works now, including: #Plex, #Jackett, #Radarr, #Sonarr, #qBittorrent, and #Overseerr. With this setup, all is needed to add a show to the media streaming frontend (will prolly explore the possibility of using #Jellyfin in place of Plex in the future) is to open up Overseerr and request for a movie/TV show - it will then contact Radarr/Sonarr to download said media using qBittorrent, after which the show will be picked up automatically by Plex.
The only "issue" left is that I notice the downloads either download slowly (hundreds of KiB/s on average), or sometimes even stall or be stuck at "downloading metadata" - even when it seems that the seeding ratio is pretty good. Dk if this is a "#Torrent" issue, or internet in a containerised environment issue (since internet speeds are fine on the host, and my own machine).
Don't really care abt said issue yet tho for now, just excited to be done with this #Helm chart as a "0.1.0" release, then improve on it further such as allowing the use of existing PVCs, external servers for each service (i.e. external qBittorrent server), etc.
RE: https://sakurajima.social/notes/9pk70gb36b -
i think i might have to separate them into several helm charts in the end lol, maybe cramming 6 containers into a single pod - which results in heavy resource usage on a single node in your cluster (rather than spread them across multi nodes), might not be the best idea.
i'll just finish the whole "master" chart, then create new charts, for each. atm, the master includes: #jackett, #overseerr, #plex, #qbittorrent, #sonarr, and #radarr. -
i think i might have to separate them into several helm charts in the end lol, maybe cramming 6 containers into a single pod - which results in heavy resource usage on a single node in your cluster (rather than spread them across multi nodes), might not be the best idea.
i'll just finish the whole "master" chart, then create new charts, for each. atm, the master includes: #jackett, #overseerr, #plex, #qbittorrent, #sonarr, and #radarr. -
i think i might have to separate them into several helm charts in the end lol, maybe cramming 6 containers into a single pod - which results in heavy resource usage on a single node in your cluster (rather than spread them across multi nodes), might not be the best idea.
i'll just finish the whole "master" chart, then create new charts, for each. atm, the master includes: #jackett, #overseerr, #plex, #qbittorrent, #sonarr, and #radarr. -
i think i might have to separate them into several helm charts in the end lol, maybe cramming 6 containers into a single pod - which results in heavy resource usage on a single node in your cluster (rather than spread them across multi nodes), might not be the best idea.
i'll just finish the whole "master" chart, then create new charts, for each. atm, the master includes: #jackett, #overseerr, #plex, #qbittorrent, #sonarr, and #radarr. -
Iβve managed to open my #overseerr #docker container to the internet through a #cloudflare Argo tunnel. Itβs from the Cloudflared #homeassistant addon, which is used to open home assistant too. Iβm wondering if it is safe, and what can I do to make it more secure. #linux #selfhosted
-
My #plex / #jellyfin folk. What do you guys use for your media discovery. I'm currently using #overseerr but that seems to not be the most active as a project. It works and works well but don't wanna keep running on software that's not that active. Looking to see if there is anything else out there.
-
@mcontreras @cepeda Alguien sabe como configurar las Notificaciones de Telegram en #Overseerr ?
-
Ci sono poche cose che mi rendono felici: La mia famiglia, i miei amici e il mio #raspberrypi zeppo di container docker tra cui #homeassistant #sonarr #radarr #overseerr #aria2c con il carico della cpu a 15m inferiore a 1.0