mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2026-11-06 15:28:18 +00:00
Fix Dead Links (#129)
This commit is contained in:
1 parent
77184f5937
commit
6892542f9d
51 files changed
+354
-361
No files matched your search
@@ -1,5 +1,5 @@
|
||||
!!! warning
|
||||
This is not a complete recipe - it's a component of the [autopirate](/recipes/autopirate/) "_uber-recipe_", but has been split into its own page to reduce complexity.
|
||||
This is not a complete recipe - it's a component of the [autopirate](/recipes/autopirate/) "_uber-recipe_", but has been split into its own page to reduce complexity.
|
||||
|
||||
# Jackett
|
||||
|
||||
@@ -13,7 +13,7 @@ This allows for getting recent uploads (like RSS) and performing searches. Jacke
|
||||
|
||||
To include Jackett in your [AutoPirate](/recipes/autopirate/) stack, include the following in your autopirate.yml stack definition file:
|
||||
|
||||
````
|
||||
```
|
||||
jackett:
|
||||
image: linuxserver/jackett:latest
|
||||
env_file : /var/data/config/autopirate/jackett.env
|
||||
@@ -44,32 +44,31 @@ jackett_proxy:
|
||||
-provider=github
|
||||
-authenticated-emails-file=/authenticated-emails.txt
|
||||
|
||||
````
|
||||
```
|
||||
|
||||
!!! tip
|
||||
I share (_with my [sponsors](https://github.com/sponsors/funkypenguin)_) a private "_premix_" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a ```git pull``` and a ```docker stack deploy``` 👍
|
||||
I share (_with my [sponsors](https://github.com/sponsors/funkypenguin)_) a private "_premix_" git repository, which includes necessary docker-compose and env files for all published recipes. This means that sponsors can launch any recipe with just a `git pull` and a `docker stack deploy` 👍
|
||||
|
||||
## Assemble more tools..
|
||||
|
||||
Continue through the list of tools below, adding whichever tools your want to use, and finishing with the **[end](/recipes/autopirate/end/)** section:
|
||||
|
||||
* [SABnzbd](/recipes/autopirate/sabnzbd.md)
|
||||
* [NZBGet](/recipes/autopirate/nzbget.md)
|
||||
* [RTorrent](/recipes/autopirate/rtorrent/)
|
||||
* [Sonarr](/recipes/autopirate/sonarr/)
|
||||
* [Radarr](/recipes/autopirate/radarr/)
|
||||
* [Mylar](/recipes/autopirate/mylarr/)
|
||||
* [Lazy Librarian](/recipes/autopirate/lazylibrarian/)
|
||||
* [Headphones](/recipes/autopirate/headphones)
|
||||
* [Lidarr](/recipes/autopirate/lidarr/)
|
||||
* [NZBHydra](/recipes/autopirate/nzbhydra/)
|
||||
* [NZBHydra2](/recipes/autopirate/nzbhydra2/)
|
||||
* [Ombi](/recipes/autopirate/ombi/)
|
||||
* Jackett (this page)
|
||||
* [Heimdall](/recipes/autopirate/heimdall/)
|
||||
* [End](/recipes/autopirate/end/) (launch the stack)
|
||||
|
||||
- [SABnzbd](/recipes/autopirate/sabnzbd.md)
|
||||
- [NZBGet](/recipes/autopirate/nzbget.md)
|
||||
- [RTorrent](/recipes/autopirate/rtorrent/)
|
||||
- [Sonarr](/recipes/autopirate/sonarr/)
|
||||
- [Radarr](/recipes/autopirate/radarr/)
|
||||
- [Mylar](/recipes/autopirate/mylar/)
|
||||
- [Lazy Librarian](/recipes/autopirate/lazylibrarian/)
|
||||
- [Headphones](/recipes/autopirate/headphones)
|
||||
- [Lidarr](/recipes/autopirate/lidarr/)
|
||||
- [NZBHydra](/recipes/autopirate/nzbhydra/)
|
||||
- [NZBHydra2](/recipes/autopirate/nzbhydra2/)
|
||||
- [Ombi](/recipes/autopirate/ombi/)
|
||||
- Jackett (this page)
|
||||
- [Heimdall](/recipes/autopirate/heimdall/)
|
||||
- [End](/recipes/autopirate/end/) (launch the stack)
|
||||
|
||||
## Chef's Notes 📓
|
||||
|
||||
1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
|
||||
1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. "radarr"), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
|
||||
Reference in new issue
Block a user