Stage_log : list of actions taken by SABnzbd to download/processĭownloaded_to : file/directory this NZB was downloaded to Postproc_time : time in seconds it took to postprocess this NZB
SABNZBD CATEGORIES DOWNLOAD
Incomplete_path: path where SABnzbd stored incomplete download Id : internal id (not the same as `nzbid`) the output of the history command, with, again, an extra entries propertyĪ normalized history entry contains the following properties:Ĭompleted : completed timestamp, as Date objectįail_message : message why download failed.Otherwise, just resumes downloading of a single NZB. Without arguments, resumes the entire queue. Otherwise, just pauses downloading of a single NZB. Without arguments, pauses the entire queue. Optional object any of the following options pp=Post Process Level, script=Post Process Script, cat=Category, priority=Priority.See lete() for arguments.Īdd an NZB to the queue by URL, with optional arguments.
_queue_slot : boolean (always true) to identify this as a queue entry Time_left : time left before download should be complete, in seconds 'Failed', 'Verifying', 'Downloading', 'Extracting') Status : download status ('Completed', 'Paused', 'Queued, Size_left : number of bytes still to download before completion (for all commands and their arguments, check the the SABnzbd API page)įor example, the version() method is implemented like this:
SABNZBD CATEGORIES HOW TO
API key (required for most operations, see Install on how to get it).Commands Common commands new SABnzbd(URL, API_KEY) Sabnzbd is Promise based, so all commands return a promise. Another thing is that the SABnzbd API is not terribly informative on the status of some commands for instance, the remove commands will always return a true status, even if you're using an nonexistent NZB id. However, because the SABnzbd API is horribly inconsistent at times, I've added some normalization (see the status and entries commands) to make interfacing with it a bit easier. commands related to the SABnzbd history (the list of completed downloads)įor the most part, the client implements the commands found on the SABnzbd API page, and returns their results pretty much as-is.commands related to the SABnzbd queue (the list of currently active downloads).in the SABnzbd Web Server settings, find the API key (or generate one).open the SABnzbd web interface in your browser.If after running the automatic update, CouchPotato will not start, try this as root user:Ĭhmod 755 /var/hda/web-apps/couchpotato/html/CouchPotato.You'll also need the API key for your SABnzbd installation:
SABNZBD CATEGORIES CODE
The last step is to reload apache, again for Ubuntu the code is: Look for the lines beginning ProxyPass and ProxyPassReverse and modify the port. This needs to be done as root, for Ubuntu the code is: You are looking for a file named something like ****nf, next open the file up and edit it to reflect the new port chosen. This can be rectified by modifying the http conf file to point to the new port.
SABNZBD CATEGORIES PC
NOTE: Proceed with care, this information is outdated. CouchPotato can be accessed from -or- yourHDAip:5000 (i.e.
0 kommentar(er)
