Concepts
Weaver’s UI and docs reuse a small set of terms. Learn them once and the rest of the app reads consistently.
- Jobs And Queue: instance, NZB, job, job statuses, priority, queue, categories, history, and duplicate handling.
- Pipeline And Storage: the three directories, pipeline stages, direct store, delivery naming, and post-processing scripts.
- Servers And Bandwidth: servers, groups, backfill, retention, quotas, speed limits, the ISP cap, and schedules.
- Automation And Integration: RSS, the watch folder, API keys, the GraphQL and NZBGet-compatible APIs, metrics, and backups.
Easy To Confuse Pairs
Section titled “Easy To Confuse Pairs”| Pair | Difference |
|---|---|
| Queue vs History | The queue is live work. History is the retained record of finished and failed work. |
| Job vs NZB | The NZB is the file you submit. The job is the work Weaver tracks from it. |
| Category vs directory | A category is a label and routing rule. The directory is the destination it may choose. |
| Speed limit vs bandwidth cap | A speed limit controls rate. The ISP bandwidth cap controls a byte allowance per window. |
| Group vs backfill | Group orders servers. Backfill holds a server back for articles the others could not supply. |
| Direct store vs incremental extraction | Direct store never writes archive volumes. Incremental extraction writes them and unpacks while downloading. |
| Global pause vs job pause | Global pause stops dispatch across the queue. A job pause holds one job. |
| Backup vs payload files | A backup carries settings and history. It never includes downloaded files. |