exfile v0.3.4 Exfile.Backend.FileSystem
A local filesystem-backed backend.
FileSystem accepts the standard initialization options, plus one:
:ttl
— configurable TTL (in seconds) for files stored in the backend. Files are checked and vacuumed on initialization or by callingvacuum/1
manually. Note that the mtime (file modification timestamp) is used to determine if a file should be deleted or not. This option only makes sense in an ephemeral cache configuration, never a persistent store.
Summary
Functions
Callback implementation for Exfile.Backend.delete/2
Callback implementation for Exfile.Backend.exists?/2
Callback implementation for Exfile.Backend.get/2
Callback implementation for Exfile.Backend.init/1
Callback implementation for Exfile.Backend.open/2
Callback implementation for Exfile.Backend.path/2
Callback implementation for Exfile.Backend.size/2
Callback implementation for Exfile.Backend.upload/2
Scan & delete files in backend that have expired
Functions
Callback implementation for Exfile.Backend.delete/2
.
Callback implementation for Exfile.Backend.exists?/2
.
Callback implementation for Exfile.Backend.get/2
.
Callback implementation for Exfile.Backend.init/1
.
Callback implementation for Exfile.Backend.open/2
.
Callback implementation for Exfile.Backend.path/2
.
Callback implementation for Exfile.Backend.size/2
.
Callback implementation for Exfile.Backend.upload/2
.
Specs
vacuum(Exfile.Backend.t) :: :ok | {:error, :file.posix}
Scan & delete files in backend that have expired
No-op when the :ttl
option is “infinity” or nil (default).