Runtime Data

SynapS3 stores configuration, metadata, and cached object data on local disk. For long-running nodes, place this data on durable storage and back it up before upgrades.

Default Local Layout

~/.synaps3/
  config.toml
  db/
    synaps3.db
    synaps3.db-shm
    synaps3.db-wal
  cache/

SQLite WAL and SHM files are expected. Explicit database.dsn and cache.dir values take precedence over defaults.

Docker Layout

The container uses /var/lib/synaps3:

/var/lib/synaps3/
  config.toml
  db/
  cache/

The Compose deployment mounts this path through the synaps3-data Docker volume.

What Must Be Durable

Data	Why it matters
config.toml	Holds stable runtime settings when they are not environment-managed.
db/	Stores buckets, objects, versions, tasks, users, and storage metadata.
cache/	Holds locally durable object bytes before and after Filecoin upload.
Environment secrets	May hold the Filecoin private key and deployment-specific overrides.

Cache Policy

cache.eviction_policy = "lru" queues local cache eviction after remote storage succeeds. It is not a scanner for arbitrary old files.

Default capacity settings are conservative for a single node:

[server]
max_connections = 4096
max_requests = 512

[database]
max_open_conns = 4
max_idle_conns = 2

[cache]
max_size_gb = 100
eviction_policy = "lru"

Backup Example

For Docker Compose:

docker run --rm \
  -v synaps3-data:/data:ro \
  -v "$PWD":/backup \
  alpine:3 \
  tar czf /backup/synaps3-data.tgz -C /data .

Expected result: the archive contains config, database, and cache data from the volume.

Operator Checks

synaps3 admin status
synaps3 admin settings get cache.max_size_gb

Expected result: the status output shows cache usage and worker health. If cache usage approaches capacity, see Troubleshooting.