Storage¶

Persistent mode uses one SQLite database per service, with WAL and versioned migrations. API calls use transactions. --durable selects SQLite's synchronous=FULL setting. Ephemeral mode uses in-memory databases and temporary S3 files.

S3 files¶

Current object bodies mirror the bucket and key layout:

roto-data/
  s3/
    <bucket>/<key path>
    .roto/

Non-current versions and in-flight multipart parts live under .roto. Writes use a temporary file followed by an atomic rename. When a key is also a prefix, such as a alongside a/b, the object at a is stored as a/.roto-self. Unsafe or overly long key segments are escaped.

SQLite remains the source of truth for metadata and listings. You can browse or copy the file tree, but copying new files into a bucket directory does not register new objects. Upload fixtures through the S3 API.

Current limits¶

The planned S3 rescan command, crash-recovery reconciliation, and additional filesystem fsync controls are not implemented. Treat the on-disk format as under development. See Server reference for storage options and the reset endpoint.