-
Notifications
You must be signed in to change notification settings - Fork 16
Watchfolder Configuration
Watchfolders are configured separately from the main configuration because you can have multiple watchfolders each with their own settings.
Watchfolders are configured in the userconf/watchfolders directory. For each watchfolder you want to monitor make a copy of readme.txt to a file with an .ini extension (10-default.ini for instance)
This uniquely identifies the folder to the uploader. This is also the name that will be used in subfolders for backup and postingfailed folders when moving over the files, so make sure this is a valid directory name for your OS.
If more than one ini file has the same short name the latest one (alphabetically) will overwrite settings of the previous file.
The folder path to monitor.
Relative paths can be used by not starting with a /
When this setting is set to yes files will be uploaded with a guid instead of the filename. This makes it so that from just the messages on usenet it is not easy to determine what file is contained within the post.
wether or not to clean the name before posting on usenet.
This performs the following actions on the filename:
- Any non ascii characters are removed
- All spaces are replaced by
. - All plusses are replaced by
. - Ampersand (
&) is replaced byand - Any of the following characters are removed:
()=@#$%^,?<>{}| - Double dots after eachother get replaced by a single
.
For some file types that break the usual usenet naming convention (anime for example) you want to have this turned off.
A prefix to add to every release name, leave blank to omit
A suffix to add to every release name, leave blank to omit
What newsgroups to upload to, specify more than one with a pipe character (|) in between.
Like a.b.multimedia|a.b.test|a.b.videos
What address the messages will be posted from. This is a purely theorethical setting. But it has to be filled in with some value. Feel free to let it set to the default setting.
When this is set to yes a random password will be applied to the created rar files. It is highly reccommended to enable the NSB output folder in this case. Because the nzb will contain the password. Otherwise you will have to look into the sqlite3 database to know the password that has been used on the release.
Apply a fixed password to the created rar files. Attention, if ApplyRandomPassword is set to yes this setting will be ignored
The priority of this watchfolder. Folders with higher priority jump the queue and will be picked up next before watchfolders of a lower priority (that does mean the current upload will be finished first)