copyparty/docs/rclone.md

using rclone to mount a remote copyparty server as a local filesystem

speed estimates with server and client on the same win10 machine:

• 1070 MiB/s with rclone as both server and client
• 570 MiB/s with rclone-client and copyparty -ed -j16 as server
• 220 MiB/s with rclone-client and copyparty -ed as server
• 100 MiB/s with ../bin/copyparty-fuse.py as client

when server is on another machine (1gbit LAN),

• 75 MiB/s with ../bin/copyparty-fuse.py as client
• 92 MiB/s with rclone-client and copyparty -ed as server
• 103 MiB/s (connection max) with copyparty -ed -j16 and all the others

creating the config file

if you want to use password auth, add headers = Cookie,cppwd=fgsfds below

on windows clients:

(
echo [cpp]
echo type = http
echo url = http://127.0.0.1:3923/
) > %userprofile%\.config\rclone\rclone.conf

also install the windows dependencies: winfsp

on unix clients:

cat > ~/.config/rclone/rclone.conf <<'EOF'
[cpp]
type = http
url = http://127.0.0.1:3923/
EOF

mounting the copyparty server locally

rclone.exe mount --vfs-cache-max-age 5s --attr-timeout 5s --dir-cache-time 5s cpp: Z:

use rclone as server too, replacing copyparty

feels out of place but is too good not to mention

rclone.exe serve http --read-only .

• webdav gives write-access but http is twice as fast
• ftp is buggy, avoid

bugs

• rclone-client throws an exception if you try to read an empty file (should return zero bytes)