Expand description
Utilities for working with mutable stores.
Structs
- The default
MutableStore, which simply uses the filesystem. This is suitable for development and production environments with writable filesystems (in which it’s advised), but this is of course not usable on production read-only filesystems, and another implementation ofMutableStoreshould be preferred.
Traits
- A trait for implementations of stores that the Perseus engine can use for mutable data, which may need to be altered while the server is running. In exported apps, this is irrelevant, since there is no server process to speak of. This store is used in particular by the revalidation and incremental generation strategies, which will both update build artifacts for future caching. By default,
FsMutableStoreis used for simplicity and low latency, though this is only viable in deployments with writable filesystems. Notably, this precludes usage in serverless functions.