Enderchest
Documentation · rclone

rclone with Enderchest

Set up rclone against Enderchest in two minutes: one remote in rclone.conf, then copy, sync, mount and check work as they do against any S3 bucket.

Endpoint https://s3.enderchest.store · region eu-ams-1 · path-style addressing · an access key from the console. 50 GB free on every account, then $3 per TB per month; downloads and API requests are free.

Add a remote to ~/.config/rclone/rclone.conf, or run rclone config and choose Amazon S3 Compliant Storage Providers, provider Other.

[enderchest]
type = s3
provider = Other
endpoint = https://s3.enderchest.store
region = eu-ams-1
force_path_style = true
access_key_id = YOUR_ACCESS_KEY_ID
secret_access_key = YOUR_SECRET_ACCESS_KEY
upload_cutoff = 64M
chunk_size = 64M
upload_concurrency = 4

Then use the remote like any other:

rclone mkdir enderchest:backups
rclone copy  /data/photos enderchest:backups/photos --progress
rclone sync  /data/photos enderchest:backups/photos --progress
rclone ls    enderchest:backups
rclone check /data/photos enderchest:backups/photos
rclone mount enderchest:media /mnt/media --vfs-cache-mode full --read-only

chunk_size controls multipart part size; 64M is a good default for a home connection, and larger parts (up to 5G) suit fast links. upload_concurrency parts are in flight at once, so memory use is roughly chunk_size × upload_concurrency.

For rclone mount with a media player, prefer a read-only key and --vfs-cache-mode full so seeks are served from the local cache.

Other clients

Every supported operation is listed in the documentation. Questions: [email protected].