The memory backend is an in RAM backend. It does not persist its data - use the local backend for that.
The memory backend behaves like a bucket based remote (e.g. like
s3). Because it has no parameters you can just use it with the
:memory: remote name.
You can configure it as a remote like this with
rclone config too if
you want to:
No remotes found - make a new one n) New remote s) Set configuration password q) Quit config n/s/q> n name> remote Type of storage to configure. Enter a string value. Press Enter for the default (""). Choose a number from below, or type in your own value [snip] XX / Memory \ "memory" [snip] Storage> memory ** See help for memory backend at: https://rclone.org/memory/ ** Remote config -------------------- [remote] type = memory -------------------- y) Yes this is OK (default) e) Edit this remote d) Delete this remote y/e/d> y
Because the memory backend isn't persistent it is most useful for testing or with an rclone server or rclone mount, e.g.
rclone mount :memory: /mnt/tmp rclone serve webdav :memory: rclone serve sftp :memory:
The memory backend supports MD5 hashes and modification times accurate to 1 nS.
The memory backend replaces the default restricted characters set.