Skip to main content
By default, Noēsis writes episodes under ./.noesis/episodes/<episode-id>/. In a team or service setting, you usually want a shared location so everyone can see/replay the same traces. This guide shows four common setups:
  1. Network volume (NFS/SMB)
  2. Local + S3 sync
  3. Docker bind mount
  4. Kubernetes PersistentVolumeClaim
Pick one of these patterns for your environment—you don’t need all four.

A) Shared dev: network volume

Configure your app/runtime to use it as the base runs directory, e.g.:
Result: /srv/noesis/episodes/<service>/<episode-id>/ is shared across the team.

B) Shared dev: local + S3 (or any object store)

Don’t write directly to S3; sync a local directory.
Pattern: local path for fast replay/debugging, S3 as central archive.

C) Docker: bind-mount the runs directory

Inside the container, Noēsis writes to /app/.noesis/episodes/...; on the host, you see /srv/noesis/episodes/....

D) Kubernetes: PersistentVolumeClaim

Each pod writes episodes under /var/noesis/episodes, backed by the shared PVC.
If you can answer “Where do episodes live in this environment?” and “Who can read them?”, you’re ready to roll Noēsis out beyond your laptop.