In the previous post we saw how to set up a Homemade Netflix. In this post, we're going to take a look at what we will need to feed our media server with content.
As in previous posts, I recommend having some knowledge of Docker before continuing. And don’t forget all this code is on GitHub, give it a star ⭐.
This post is the start of a series where we’ll see what these tools are and how to set everything up automatically. All the code shown in these posts can be run directly in the docker-compose file, or through Portainer.
1 - Infrastructure to Get Content
No matter what type of content you want to get, music, movies, books, TV shows, or subtitles, the architecture is going to be the same, and it will include the following elements:
- Torrent client
- Torrent indexer
- Content manager
And a small diagram would look like this:
Unfortunately, there isn’t a script or something similar to configure everything with a single command. These are open source applications that are interrelated and, as I asked a few months ago, the answer was no, they’re not going to make something to set everything up easily, so there are a few manual steps involved.
Over the coming days, I’ll be posting a series of posts with the configuration for each one. The list is as follows (I’ll update with links as they become available):
- Transmission for torrents
- Prowlarr for the indexers
- Sonarr for the TV Series library
- Radarr for the Movie library
- Lidarr for the Audio library
- Readarr for the Book library
- Bazarr for subtitles
- Overserr for recommendations.
I’ll be updating this post with corresponding links as I publish the posts.
If there is any problem you can add a comment bellow or contact me in the website's contact form
