Jackett | API Support for your favorite torrent trackers | Stream Processing library

by Jackett C# Version: v0.21.207 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | Jackett Summary

Jackett is a C# library typically used in Data Processing, Stream Processing, Nodejs, Docker applications. Jackett has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has medium support. You can download it from GitHub.

This project is a new fork and is recruiting development help. If you are able to help out please contact us. Please see our troubleshooting and contributing guidelines before submitting any issues or pull requests. Jackett works as a proxy server: it translates queries from apps (Sonarr, Radarr, SickRage, CouchPotato, Mylar3, Lidarr, DuckieTV, qBittorrent, Nefarious etc.) into tracker-site-specific http queries, parses the html or json response, and then sends results back to the requesting software. This allows for getting recent uploads (like RSS) and performing searches. Jackett is a single repository of maintained indexer scraping & translation logic - removing the burden from other apps. Developer note: The software implements the Torznab (with hybrid nZEDb/Newznab category numbering) and TorrentPotato APIs. A third-party Golang SDK for Jackett is available from webtor-io/go-jackett. Trackers marked with have no active maintainer and may be missing features or be broken. If you have an invite for them please send it to garfieldsixtynine -at- gmail.com to get them fixed/improved.

Support

Quality

Security

License

Reuse

Support

Jackett has a medium active ecosystem.

It has 9256 star(s) with 1075 fork(s). There are 177 watchers for this library.

It had no major release in the last 12 months.

There are 197 open issues and 11137 have been closed. On average issues are closed in 411 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Jackett is v0.21.207

Quality

Jackett has 0 bugs and 0 code smells.

Security

Jackett has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Jackett code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Jackett is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

Jackett releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 5058 lines of code, 0 functions and 308 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Jackett

Get all kandi verified functions for this library.

Jackett Key Features

No Key Features are available at this moment for Jackett.

Jackett Examples and Code Snippets

No Code Snippets are available at this moment for Jackett.

Community Discussions

Trending Discussions on Jackett

Routing all net traffic from a k8s container through another in the same pod

Docker containers disappear without trace

QUESTION

Routing all net traffic from a k8s container through another in the same pod

Asked 2021-Jan-19 at 15:44

I'm using GKE for deployments.

Edit: I need to access a customer's API endpoint which is only accessible when using their VPN. So far I can run a container which connects to this VPN and I can cURL the endpoint successfully.

For the above, I have configured a Debian docker image which successfully connects to a VPN (specifically, using Kerio Control VPN) when deployed. Whenever I make a net request from this container, it runs through the VPN connection, as expected.

I have another image which runs a .NET Core program which makes necessary HTTP requests.

From this guide I know it is possible to run a container's traffic through another using pure docker. Specifically using the --net=container:something option (trimmed the example):

...

ANSWER

Answered 2021-Jan-16 at 20:24

Each container in pod have shared network resources. If you run vpn client in one container them all containers in this pod will have access to network via vpn.

Source https://stackoverflow.com/questions/65753902

QUESTION

Docker containers disappear without trace

Asked 2020-Aug-12 at 10:08

I'm running Ubuntu Server 18.04, Docker 19.03.12, and Compose 1.25.0.

I run several applications through my Docker compose file (example below). Recently, some containers (mainly Jackett but once Deluge) will completely disappear, they don't show with docker ps -a, and I can't access their logs because the container doesn't exist.

I don't really know how to go about diagnosing this because there doesn't seem to be any trail to follow.

Jackett service entry

...

ANSWER

Answered 2020-Aug-12 at 10:08

It turns out the issue appears to be Ouroboros. I was thinking what would have access to starting and stopping docker containers, and I had a look in the Ouroboros logs and found this:

Source https://stackoverflow.com/questions/63337998

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Jackett

We recommend you install Jackett as a Windows service using the supplied installer. You may also download the zipped version if you would like to configure everything manually.
Check if you need any .NET prerequisites installed, see https://docs.microsoft.com/en-us/dotnet/core/install/windows?tabs=net60#dependencies
Download the latest version of the Windows installer, "Jackett.Installer.Windows.exe" from the releases page.
When prompted if you would like this app to make changes to your computer, select "yes".
If you would like to install Jackett as a Windows Service, make sure the "Install as Windows Service" checkbox is filled.
Once the installation has finished, check the "Launch Jackett" box to get started.
Navigate your web browser to http://127.0.0.1:9117
You're now ready to begin adding your trackers and using Jackett.
On most operating systems all the required dependencies will already be present. In case they are not, you can refer to this page https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md.
A) Command to download and install latest package and run the Jackett service:.
Download and extract the latest Jackett.Binaries.LinuxAMDx64.tar.gz release from the releases page
To install Jackett as a service, open a Terminal, cd to the jackett folder and run sudo ./install_service_systemd.sh You need root permissions to install the service. The service will start on each logon. You can always stop it by running systemctl stop jackett.service from Terminal. You can start it again it using systemctl start jackett.service. Logs are stored as usual under ~/.config/Jackett/log.txt and also in journalctl -u jackett.service.
On most operating systems all the required dependencies will already be present. In case they are not, you can refer to this page https://github.com/dotnet/core/blob/master/Documentation/linux-prereqs.md.
Download and extract the latest Jackett.Binaries.LinuxARM32.tar.gz or Jackett.Binaries.LinuxARM64.tar.gz (32 bit is the most common on ARM) release from the releases page
To install Jackett as a service, open a Terminal, cd to the jackett folder and run sudo ./install_service_systemd.sh You need root permissions to install the service. The service will start on each logon. You can always stop it by running systemctl stop jackett.service from Terminal. You can start it again it using systemctl start jackett.service. Logs are stored as usual under ~/.config/Jackett/log.txt and also in journalctl -u jackett.service.
If you want to run it with a user without a /home directory you need to add Environment=XDG_CONFIG_HOME=/path/to/folder to your systemd file, this folder will be used to store your config files. Mono must be compiled with the Roslyn compiler (default), using MCS will cause "An error has occurred." errors (See https://github.com/Jackett/Jackett/issues/2704).
Install Mono 5.8 or better (using the latest stable release is recommended) Follow the instructions on the mono website and install the mono-devel and the ca-certificates-mono packages. On Red Hat/CentOS/openSUSE/Fedora the mono-locale-extras package is also required.
Install libcurl: Debian/Ubuntu: apt-get install libcurl4-openssl-dev Redhat/Fedora: yum install libcurl-devel For other distros see the Curl docs.
Download and extract the latest Jackett.Binaries.Mono.tar.gz release from the releases page and run Jackett using mono with the command mono --debug JackettConsole.exe.
(Optional) To install Jackett as a service, open the Terminal and run sudo ./install_service_systemd_mono.sh You need root permissions to install the service. The service will start on each logon. You can always stop it by running systemctl stop jackett.service from Terminal. You can start it again it using systemctl start jackett.service. Logs are stored as usual under ~/.config/Jackett/log.txt and also in journalctl -u jackett.service.
On a CentOS/RedHat 7 system: jewflix.jackett. On an Ubuntu 16 system: chrisjohnson00.jackett.
The service will start on each logon. You can always stop it by running launchctl unload ~/Library/LaunchAgents/org.user.Jackett.plist from Terminal. You can start it again it using launchctl load ~/Library/LaunchAgents/org.user.Jackett.plist. Logs are stored as usual under ~/.config/Jackett/log.txt.
Download and extract the latest Jackett.Binaries.macOS.tar.gz or Jackett.Binaries.macOSARM64.tar.gz release from the releases page.
Open the extracted folder and double-click on install_service_macos.
If the installation was a success, you can close the Terminal window.
Detailed instructions are available at LinuxServer.io Jackett Docker. The Jackett Docker is highly recommended, especially if you are having Mono stability issues or having issues running Mono on your system e.g. QNAP, Synology. Thanks to LinuxServer.io.
Jackett is available as a beta package from SynoCommunity.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: