#jackett — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jackett, aggregated by home.social.
-
Después de algunos intentos fallidos,el fin de semana pasado pude instalar y configurar el plugin jackett en qbittorrent, que amplia a otros buscadores. Aún no tengo claro el alcance, o cuánto agrega a lo que busco a veces, pero ya veremos.
https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin
-
Después de algunos intentos fallidos,el fin de semana pasado pude instalar y configurar el plugin jackett en qbittorrent, que amplia a otros buscadores. Aún no tengo claro el alcance, o cuánto agrega a lo que busco a veces, pero ya veremos.
https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin
-
Después de algunos intentos fallidos,el fin de semana pasado pude instalar y configurar el plugin jackett en qbittorrent, que amplia a otros buscadores. Aún no tengo claro el alcance, o cuánto agrega a lo que busco a veces, pero ya veremos.
https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin
-
Después de algunos intentos fallidos,el fin de semana pasado pude instalar y configurar el plugin jackett en qbittorrent, que amplia a otros buscadores. Aún no tengo claro el alcance, o cuánto agrega a lo que busco a veces, pero ya veremos.
https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin
-
Después de algunos intentos fallidos,el fin de semana pasado pude instalar y configurar el plugin jackett en qbittorrent, que amplia a otros buscadores. Aún no tengo claro el alcance, o cuánto agrega a lo que busco a veces, pero ya veremos.
https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin
-
TRaSH-Guides is a comprehensive collection of guides for Radarr, Sonarr, and related media management tools. These guides answer common questions and provide the best settings for your entire media server setup.
https://trash-guides.info/ -
TRaSH-Guides is a comprehensive collection of guides for Radarr, Sonarr, and related media management tools. These guides answer common questions and provide the best settings for your entire media server setup.
https://trash-guides.info/ -
Falsche Polizisten stehlen Schmuck und Geld
Eine 88-jährige Seniorin hat am Montagnachmittag auf der Polizeiwache Walsum einen Betrug angezeigt. Die ältere Frau schilderte, dass…
##Duisburg Deutschland #Deutsch #DE #Schlagzeilen #Headlines #Nachrichten #News #Europe #Europa #EU #Duisburg #abgehoben #circa #Deutschland #Germany #Jackett #Kürze #Nordrhein-Westfalen #Polizist #Schmuck #Seniorin #unbekannten #Wohnung
https://www.europesays.com/de/197509/ -
I love the way jackett updates itself. The program runs on different OS smoothly, is an sh based program, only does one thing and does it excellent.
The Update process is run only after a long while, after the spawn of jackett. Since I always monitor its logs i saw the following (as screencapped) today when it announced a new version.
Every move it makes is logged in explicit detail. You see how a lib is first copied checked after arrival then replacing the old version. The same goes for all files in the jackett tree which you run in ~/bin/jackett
#programming #opensource #POSIX #Linux #BSD #searchClient #jackett
-
I love the way jackett updates itself. The program runs on different OS smoothly, is an sh based program, only does one thing and does it excellent.
The Update process is run only after a long while, after the spawn of jackett. Since I always monitor its logs i saw the following (as screencapped) today when it announced a new version.
Every move it makes is logged in explicit detail. You see how a lib is first copied checked after arrival then replacing the old version. The same goes for all files in the jackett tree which you run in ~/bin/jackett
#programming #opensource #POSIX #Linux #BSD #searchClient #jackett
-
I love the way jackett updates itself. The program runs on different OS smoothly, is an sh based program, only does one thing and does it excellent.
The Update process is run only after a long while, after the spawn of jackett. Since I always monitor its logs i saw the following (as screencapped) today when it announced a new version.
Every move it makes is logged in explicit detail. You see how a lib is first copied checked after arrival then replacing the old version. The same goes for all files in the jackett tree which you run in ~/bin/jackett
#programming #opensource #POSIX #Linux #BSD #searchClient #jackett
-
I love the way jackett updates itself. The program runs on different OS smoothly, is an sh based program, only does one thing and does it excellent.
The Update process is run only after a long while, after the spawn of jackett. Since I always monitor its logs i saw the following (as screencapped) today when it announced a new version.
Every move it makes is logged in explicit detail. You see how a lib is first copied checked after arrival then replacing the old version. The same goes for all files in the jackett tree which you run in ~/bin/jackett
#programming #opensource #POSIX #Linux #BSD #searchClient #jackett
-
I love the way jackett updates itself. The program runs on different OS smoothly, is an sh based program, only does one thing and does it excellent.
The Update process is run only after a long while, after the spawn of jackett. Since I always monitor its logs i saw the following (as screencapped) today when it announced a new version.
Every move it makes is logged in explicit detail. You see how a lib is first copied checked after arrival then replacing the old version. The same goes for all files in the jackett tree which you run in ~/bin/jackett
#programming #opensource #POSIX #Linux #BSD #searchClient #jackett
-
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 -
Jackett и альтернативные решения (интерфейсы и api) для поиска торрентов
В этой небольшой статье расскажу о том, что такое Jackett , на сколько это полезное и простое решение в вопросе поиска нужных раздач, а также, какие существуют альтернативы как для пользовательского интерфейса, так и для API ( Application Programming Interface ).
-
Jackett и альтернативные решения (интерфейсы и api) для поиска торрентов
В этой небольшой статье расскажу о том, что такое Jackett , на сколько это полезное и простое решение в вопросе поиска нужных раздач, а также, какие существуют альтернативы как для пользовательского интерфейса, так и для API ( Application Programming Interface ).
-
Jackett и альтернативные решения (интерфейсы и api) для поиска торрентов
В этой небольшой статье расскажу о том, что такое Jackett , на сколько это полезное и простое решение в вопросе поиска нужных раздач, а также, какие существуют альтернативы как для пользовательского интерфейса, так и для API ( Application Programming Interface ).
-
@YggTorrent Le nouveau formulaire de connexion casse l'intégration avec #jackett :(
-
@YggTorrent Le nouveau formulaire de connexion casse l'intégration avec #jackett :(
-
@YggTorrent Le nouveau formulaire de connexion casse l'intégration avec #jackett :(
-
@YggTorrent Le nouveau formulaire de connexion casse l'intégration avec #jackett :(
-
@YggTorrent Le nouveau formulaire de connexion casse l'intégration avec #jackett :(
-
Jackett + Synology Download Station
Есть желание добавить в Synology Download Station возможность искать по 613 торрент трекерам? Хочется видеть, какие именно торренты будут загружены? Хочется чтобы оно работало и в мобильном приложении? Тогда прошу под кат!
https://habr.com/ru/articles/804239/
#Synology #Download_Station #jackett #кино #torrent #plex #медиацентр
-
Jackett + Synology Download Station
Есть желание добавить в Synology Download Station возможность искать по 613 торрент трекерам? Хочется видеть, какие именно торренты будут загружены? Хочется чтобы оно работало и в мобильном приложении? Тогда прошу под кат!
https://habr.com/ru/articles/804239/
#Synology #Download_Station #jackett #кино #torrent #plex #медиацентр
-
Jackett + Synology Download Station
Есть желание добавить в Synology Download Station возможность искать по 613 торрент трекерам? Хочется видеть, какие именно торренты будут загружены? Хочется чтобы оно работало и в мобильном приложении? Тогда прошу под кат!
https://habr.com/ru/articles/804239/
#Synology #Download_Station #jackett #кино #torrent #plex #медиацентр
-
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. -
An update on this - I spent about four hours yesterday trying to configure #dockercompose scripts for my services. Once I realised that you could set up multiple networked containers in one compose yml it was like a lightbulb went off. This thing is crazy powerful and useful.
I am struggling to figure out some SSL errors with #Jackett currently - I tried updating OpenSSL but didn't seem to fix it. Based on the GitHub it looks like an ongoing issue so I'm just going to hope it gets fixed soon.
The next step is moving this setup over to my host machine and configuring my port forwards correctly, then I'll switch things over to a pure docker-based setup. I'm actually really excited about learning more - maybe the next step is starting to learn a bit of #python.
-
An update on this - I spent about four hours yesterday trying to configure #dockercompose scripts for my services. Once I realised that you could set up multiple networked containers in one compose yml it was like a lightbulb went off. This thing is crazy powerful and useful.
I am struggling to figure out some SSL errors with #Jackett currently - I tried updating OpenSSL but didn't seem to fix it. Based on the GitHub it looks like an ongoing issue so I'm just going to hope it gets fixed soon.
The next step is moving this setup over to my host machine and configuring my port forwards correctly, then I'll switch things over to a pure docker-based setup. I'm actually really excited about learning more - maybe the next step is starting to learn a bit of #python.
