Skip to content

Drime

Capability Support
rclone support tier Tier 1: Core
Checksums None
Modification times Not kept: files show their upload time
Case-insensitive names No
Duplicate names allowed No
Server-side copy Yes
Server-side move and rename Yes
Folder move and rename Yes, in one step
Free space reporting Yes
Empty folders Yes
Change notifications No
Uploads of unknown size Yes
Public links No

Drime is a cloud storage and transfer service focused on fast, resilient file delivery. It offers both free and paid tiers with emphasis on high-speed uploads and link sharing.

To setup Drime you need to log in, navigate to Settings, Developer, and create a token to use as an API access key. Give it a sensible name and copy the token for use in the config.

In CloudMount you add this drive from the Add drive screen, and the wizard asks for the options listed under Options. The notes below come from rclone’s setup guide.

Drime does not support modification times or hashes.

This means that by default syncs will only use the size of the file to determine if it needs updating.

You can use the --update flag which will use the time the object was uploaded. For many operations this is sufficient to determine if it has changed. However files created with timestamps in the past will be missed by the sync if using --update.

In addition to the default restricted characters set the following characters are also replaced:

Character Value Replacement
\ 0x5C \

File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:

Character Value Replacement
SP 0x20 ␠

Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON strings.

You can set the root_folder_id for rclone. This is the directory (identified by its Folder ID) that rclone considers to be the root of your Drime drive.

Normally you will leave this blank and rclone will determine the correct root to use itself and fill in the value in the config file.

However you can set this to restrict rclone to a specific folder hierarchy.

In order to do this you will have to find the Folder ID of the directory you wish rclone to display.

You can do this with rclone

Terminal window
$ rclone lsf -Fip --dirs-only remote:
d6341f53-ee65-4f29-9f59-d11e8070b2a0;Files/
f4f5c9b8-6ece-478b-b03e-4538edfe5a1c;Photos/
d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/

The ID to use is the part before the ; so you could set

root_folder_id = d6341f53-ee65-4f29-9f59-d11e8070b2a0

To restrict rclone to the Files directory.

The wizard asks for these when you add the drive.

API Access token

You can get this from the web control panel.

Type: string

The wizard shows these under Advanced options. Most drives work without changing any of them.

ID of the root folder

Leave this blank normally, rclone will fill it in automatically.

If you want rclone to be restricted to a particular folder you can fill it in - see the docs for more info.

Type: string

Account ID

Leave this blank normally unless you wish to specify a Workspace ID.

Type: string

Number of items to list in each call

Type: int · Default: 1000

Delete files permanently rather than putting them into the trash.

Type: bool · Default: false

Cutoff for switching to chunked upload.

Any files larger than this will be uploaded in chunks of chunk_size. The minimum is 0 and the maximum is 5 GiB.

Type: SizeSuffix · Default: 5Mi

Chunk size to use for uploading.

When uploading files larger than upload_cutoff or files with unknown size (e.g. from “rclone rcat” or uploaded with “rclone mount” or google photos or google docs) they will be uploaded as multipart uploads using this chunk size.

Note that “–drime-upload-concurrency” chunks of this size are buffered in memory per transfer.

If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.

Rclone will automatically increase the chunk size when uploading a large file of known size to stay below the 10,000 chunks limit.

Files of unknown size are uploaded with the configured chunk_size. Since the default chunk size is 5 MiB and there can be at most 10,000 chunks, this means that by default the maximum size of a file you can stream upload is 48 GiB. If you wish to stream upload larger files then you will need to increase chunk_size.

Type: SizeSuffix · Default: 5Mi

Concurrency for multipart uploads and copies.

This is the number of chunks of the same file that are uploaded concurrently for multipart uploads and copies.

If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.

Type: int · Default: 4

The encoding for the backend.

See the encoding section in the overview for more info.

Type: Encoding · Default: Slash,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot

Description of the remote.

Type: string

Drime only supports filenames up to 255 bytes in length, where filenames are encoded in UTF8.