![]() All done! Your post-processing from Sabnzbd to SickGear will now run. You will notice your prompt will change to show you’re now running a virtualenv: (env) Requests sudo pip3 install requestsīack at the prompt. CD into the Sabnzbd root folder and activate virtual(env): source env/bin/activate Still SSH’d into your Synology box, you need to activate the SABnzbd Python virtual environment bundled with the app, install Requests, running the following commands. The sabToSickGear script, owned by SickGear, however, explicitly requires the Requests library, running inside SABnzbd, so you’ll have to update your SABnzbd app to include it. Neither SickGear nor SABnzbd “need” Python’s Requests library to “work” □ so you’re kind of stuck between two very small peacocks □ Go to SABnzbd, click Config Folders Post-Processing Scripts Folder and enter /share/MD0DATA/.qpkg/SickBeard/autoProcessTV (without the quotes of. Likely: # and create 3 symlinks in Sabnzbd back to SickGear’s sabnzbd scripts (using sudo): sudo ln -s sudo ln -s sudo ln -s you modify your Sabnzbd post-processing scripts for ‘tv’ - you can now select the sabToSickGear.py file. Email templates folder: For advanced users: insert the name of the folder where templates are located which can be used by SABnzbd to send certain notification e. Know where your SickGear (sickbeard-custom) and Sabnzbd install directories are. Post-processing scripts folder: For advanced users: If you want a certain script to run after downloading you have to insert the name of the folder where those script can be located.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |