Storage Layout
Storage Layout
Section titled “Storage Layout”Weaver separates durable instance state from active work and final output. Keeping those paths clear makes backups, restores, cleanup, and troubleshooting easier.
What This Page Is For
Section titled “What This Page Is For”Use this page to decide where the data directory, intermediate directory, complete directory, and category overrides should live.
Data Directory
Section titled “Data Directory”The data directory stores Weaver’s database, API keys, job cache, RSS state, backup metadata, and internal state. Keep it on persistent storage.
In Docker examples, this is usually /config.
Intermediate Directory
Section titled “Intermediate Directory”The intermediate directory stores active per-job work. Make sure Weaver can write to it and size it for in-progress jobs.
Don’t share this path with tools that expect final output only.
Complete Directory
Section titled “Complete Directory”The complete directory receives finished output after successful processing. Categories can organize or override destinations inside this boundary.
Category Overrides
Section titled “Category Overrides”Categories can define explicit destination directories. If those directories live outside the complete directory, backup restore may require path remapping.
Typical Workflows
Section titled “Typical Workflows”- Put the data directory on persistent storage before first use.
- Keep intermediate storage fast and writable.
- Keep complete storage stable and visible to downstream tools that consume finished output.
- Review category overrides before restoring from backup.