Library Layout

Scryer works best when your final media roots and completed-work staging path are explicit, stable, and mounted consistently.

If something looks wrong with paths, it’s almost always one of three issues: the final root is mounted differently than you expected, the staging path isn’t shared consistently, or the process account can’t read and write where these docs assume it can.

Recommended Container Mount Points

These are the container-side paths to target in the volumes: entries. Map host folders to these paths for a predictable layout:

/data/movies
/data/series
/data/anime
/downloads

The /data/... paths are final media roots. The /downloads path is a staging location for completed local work that Scryer may import.

These are examples, not requirements. What matters is that the paths stay stable, are visible to Scryer, and line up with the paths used by any companion service that deposits completed items.

Path Rules

These principles apply whether you run Scryer in Docker, via Homebrew, or as a manual binary:

• Keep final media paths and the completed-work staging path stable — Scryer stores them and will break if they change unexpectedly.
• Make sure the completed-work staging path is accessible at the same location for Scryer and any companion service that writes completed items.
• Avoid path translation when possible. Identical paths on both sides reduce import ambiguity.
• For Docker installs, keep Scryer’s /config volume mounted outside the container image.
• Prefer one obvious path per role instead of nested or overlapping mounts that are harder to reason about later.

Libraries And Facets

A facet defines behavior such as Movies, Series, or Anime. A library defines roots, access, scans, and destination behavior inside a facet.

For example, Movies can have more than one library if you need separate roots or access boundaries. The Movies catalog can still show all the movie titles you can access.

That separation is useful when different roots have different permissions, storage classes, or operating rules. The library boundary is where Scryer applies path ownership and access policy; the facet is where it applies shared behavior.

Pre-Flight Checklist

Before you enable monitoring and let Scryer run unattended:

• Confirm Scryer can read and write the final media roots.
• Confirm completed items are visible at the configured staging path.
• Decide whether each facet should have one library or multiple libraries.
• Run a library scan only after the roots are correct.
• Validate one real title path end to end before assuming the entire layout is ready for unattended work.

Related Concepts

• Facet — the behavior category (Movies, Series, Anime) that a library lives inside
• Library — owns roots, permissions, scans, and import destinations inside a facet
• Library scan — reconciles files on disk with Scryer’s catalog after roots are configured
• Import — how Scryer moves completed items from the staging path into a managed library root
• Monitoring — controls whether Scryer keeps evaluating a title once the layout is live