PrintStash v0.6.2: scheduled and watched shared volumes

PrintStash v0.6.2 renamed External Libraries to Shared volumes and gave each volume a better way to stay current. Local folders could react to filesystem changes, while NAS mounts kept using scheduled scans.

Choose a cron schedule

Each shared volume gained hourly, six-hourly, daily, and weekly presets plus custom cron expressions. Manual-only mode disabled background scans.

Existing fixed intervals were migrated to equivalent cron schedules where possible. Manual scans remained available in the UI and API.

Watch local folders

Local filesystem events could trigger a reconciliation within seconds. Bursts of changes were debounced before using the same safe scan path as a scheduled run.

NFS, SMB, and CIFS mounts do not reliably deliver the events needed by a container watcher. PrintStash detected network filesystems and fell back to the configured cron schedule. An Auto, On, or Off setting allowed the administrator to override detection for an unusual mount.

The Shared volumes panel showed the detected filesystem and whether watching was active, making it easier to understand why a NAS change waited for the next scan.

Migration fix

The first migration stored the new watch_mode default in a form that SQLAlchemy could not read back for existing rows. Opening Shared volumes then returned a server error. A follow-up migration corrected the default and repaired affected records.

The current shared-volume documentation covers schedules, watchers, Docker mounts, and the checks that prevent an unmounted share from looking like a mass deletion.