These instructions provide generic guidance that should apply to any Radarr Docker image. There are two common problems with Docker volumes: Paths that differ between the Radarr and download client container and paths that prevent fast moves and hard links. The second is a performance issue and causes problems for seeding torrents. Both problems can be solved with well planned, consistent paths. This causes slow moves and doesn't allow hard links because they are considered two different file systems inside the container.
Permissions and ownership of files is one of the most common problems for Radarr users, both inside and outside Docker. Most images have environment variables that can be used to override the default user, group and umask, you should decide this before setting up all of your containers. The recommendation is to use a common group for all related containers so that each container can use the shared group permissions to read and write files on the mounted volumes.
Keep in mind that Radarr will need read and write to the download folders as well as the final folders. To install and use these Docker images, you'll need to keep the above in mind while following their documentation. There are many ways to manage Docker images and containers too, so installation and maintenance of them will depend on the route you choose. Images are automatically updated multiple times in an hour if upstream changes are found.
Hotio also builds our Pull Requests which may be useful for testing. Read the instructions on how to install the image. They also maintain images for most of the popular download clients as well.
The default volumes are not optimal nor recommended. Our recommendation is to use a single volume for the data, as mentioned above. The Radarr team provides builds for BSD. Additional details can be found on Frank's GH Link. Be sure you're running the latest version of Python 2. After you've got these tools you can install the packages using npm install. Once this process has finished you can start CP using the command grunt. This will start all the needed tools and watches any files for changes.
You can now change css and javascript and it wil reload the page when needed. By default it will combine files used in the core folder. If you're adding a new. Don't forget to enable development inside the CP settings. This disables some functions and also makes sure javascript errors are pushed to console instead of the log.
Couchpotato can use either or both Usenet or torrents to download the files it finds. This raises the following question: Which one should be used? Well, the debate between Usenet and torrents is an ongoing and neverending one. In the end, they are actually quite similar although Usenet is usually faster in terms of speed of download.
For that reason, it is the option we prefer. Your experience with Couchpotato will be the same no matter what software you use but the configuration steps will, of course, be different.
Both are available for free and their installation is as easy as any other popular software. You will need them if you want to follow our Couchpotato instructions. If you want to keep them, just click Go to SABnzbd. SABnzbd is ready to use. So, from the Couchpotato homepage, simply click the OSX or Windows button, depending on your operating system.
Save the file to your computer and once the download is complete, double-click it to start the installer. Once the installer starts, just click next a couple of times, then click Install and let the installer work its magic. After a few seconds, the installation will be complete. Click Finish to quit the installer and start the application.
It really is that easy! However, installing Couchpotato is just the beginning; the bulk of the work is configuring it. Upon starting Couchpotato, instead of opening in an independent window, it will open in a browser window. Scroll down just a bit to the Basics section. You have the option to set a username and password to access Couchpotato.
If you intend to access it from a remote location, we strongly advise you to do that. It not, it is up to you. Check the box to Enable Web UI , and choose a username and password. Click the OK button at the bottom to save your changes. Click Apply and OK. Input your Host as localhost or replace with the port you used in uTorrent. To help understand CouchPotato's renaming here is a diagram. No matter which program you use to download, CouchPotato will monitor that folder as the From folder and move files to your final destination the To folder.
It will make sense in a minute. CouchPotato will monitor your From folder for new video downloads and post process them. When they are post processed the video file will have its own folder in the To folder. The From and To folder must be different for the Renamer to work. This is the key component of getting CouchPotato to work properly with usenet downloaders and torrent downloaders simultaneously, you will be feeding the downloads into the same folder CouchPotato will be watching.
You should also check Unrar in case the release you download is packaged in rar files. By default torrented CouchPotato downloads will be symbolically linked to your To folder. This is so you can still seed the torrent. If you are not interested in seeding click Show advanced settings and scroll down until you see Torrent File Action and change it to Move. If you are private trackers you probably need to seed so leave it as link if that's the case.
0コメント