Versions, trash and space

Versions

A file uploaded where one of its name is, when “Replace” is chosen, or saved from Rebodocs, is its next version; the one before stays. Restoring one makes it the newest again, as a new version with the same bytes, so the storage is not written and the restore too can be undone.

A copy

Make a copy, in the menu or the details of a file: a file of its own, beside it with “(2)” in its name, its bytes copied in the storage itself.

const copy = await client.copy(file.id);            // beside it: "budget (2).xlsx"
const mine = await client.copy(file.id, folder.id);   // or into a folder of one's own

The copy is the one who made it’s, and counts against their space; of a file shared to read, it goes to their own top. Its smaller pictures and its text go with it. S3, Azure and the disk copy the bytes themselves; Google Cloud Storage has them read and written by the server, up to 100 MB.

The trash

A folder goes in with all that is in it, and comes back the same, where it was. Deleting from the trash takes the bytes from the bucket, of every version. ⌘Z, or Undo in the toast, takes back the last trash, move, rename or colour.

Space, and a trash that empties itself

createDriveHandler({
  ...options,
  // Or from the settings of the drive, under Storage, for whoever may configure it.
  settings: { quota: 5 * 1024 ** 3, trashDays: 30 },
});

An upload past one’s quota is refused before anything goes (413 over-quota); every version counts, in the trash too. The side of the drive shows the space one uses, of how much. The trash is looked at every ten minutes, as requests come, and what has been in it the days said is deleted, its bytes with it.