Disable caching for Seafile Drive Client

I’d like to have an option to completely disable caching of the Seafile Drive Client because it will increase ssd aging and eats up disk space. For example if I use it for getting through my pictures, I maybe watch pictures from one directory today and from another directory tomorror. It’s unlikely that I will open the same pictures everyday, so the caching is not really useful for this usecase.


Thanks for suggestion. We’ll keep this in mind. If more users require this, we’ll add it.


Maybe you can add something like RAM-Cache, so the content won’t be written to the disk for days, but only to the RAM, e.g. 100MB - whatever is used at this moment.
I don’t know how you will implement encrypted libraries, but this could also apply to them: I don’t want to have unencrypted content written to the disk.

Hello, folks.
I would agree an that, a possibility to disable Caching would be very nice to have.
A can only agree to those arguments mentioned before by @Garfield.

I also do have a laptop with just 128Gb SSD inside, well, it’s fine, but what I would like is simply to backup my data in Seafile - and that’s it, I do not need a Cached folder with twice the data on my hard drive :slight_smile:

Thank you very much for your effort!

PS.: This two scenarios could be realized by adding the functionality :slight_smile:

That circumstance is currently preventing me from using the drive.
Would be awesome if you could add it! :heart_eyes:

+1 Would be nice to have!


Would be a nice feature!

I’d be also nice to select the drive cache folder, so I can select another disk and not my system drive.

Just to let all of you know.
It’s now actually planned to be released. See below reply from Daniel.

seadrive-data-folder-location SeaDrive Data Folder Location:

I second that. Would be great to be able to completely disable local caching

I would really like this feature. Just being able to use cache-RAM would be very nice

1 Like

If you are running on linux you already have that option via mounting tmpfs on the cache folder with fixed capacity or by creating and configuring a folder in /dev/shm/