Skip to main content

🔄 rclone

rclone is ideal for syncing large directory trees and automated backups to Lighthouse.

Setup​

Add this to ~/.config/rclone/rclone.conf:

[lighthouse]
type = s3
provider = Other
access_key_id = YOUR_ACCESS_KEY
secret_access_key = YOUR_SECRET_KEY
region = us-east-1
endpoint = https://s3.lighthouse.storage
force_path_style = true

(Or run rclone config interactively: choose s3 → Other, and enter the same values.)

Use it​

# create a bucket
rclone mkdir lighthouse:backups

# copy a directory
rclone copy ~/documents lighthouse:backups/documents --progress

# incremental sync (only transfers changes)
rclone sync ~/photos lighthouse:backups/photos --progress

# verify
rclone ls lighthouse:backups
rclone check ~/photos lighthouse:backups/photos

Tips​

  • --transfers 8 parallelizes uploads of many small files.
  • --s3-upload-cutoff 100M --s3-chunk-size 32M tunes when multipart kicks in and the part size for very large files.
  • rclone's check compares checksums: Lighthouse S3 returns standard MD5 ETags for single-part uploads, so integrity verification works as on Amazon S3.
Backups and content addressing

Every synced file gets an IPFS CID (visible via rclone lsjson --metadata or a HeadObject call). For long-term archives this gives you cryptographic proof of content integrity for free.