rclone/docs/content/memory.md
Nick Craig-Wood c789436580 The memory backend
This is a bucket based remote
2020-01-18 10:41:08 +00:00

67 lines
1.7 KiB
Markdown

---
title: "Memory"
description: "Rclone docs for Memory backend"
date: "2020-01-18"
---
<i class="fas fa-memory"></i> Memory
-----------------------------------------
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 (eg 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, eg
rclone mount :memory: /mnt/tmp
rclone serve webdav :memory:
rclone serve sftp :memory:
### Modified time and hashes ###
The memory backend supports MD5 hashes and modification times accurate to 1 nS.
#### Restricted filename characters
The memory backend replaces the [default restricted characters
set](/overview/#restricted-characters).
<!--- autogenerated options start - DO NOT EDIT, instead edit fs.RegInfo in backend/memory/memory.go then run make backenddocs -->
<!--- autogenerated options stop -->