- Queries
- All Atoms
- Search
- Advanced Search
Diviner All Atoms
All Atoms
All Atoms
- Local disk storage engine. Keeps files on local disk. This engine is easy to set up, but it doesn't work if you have multiple web frontends!
- Class
- Convert a handle into an absolute local disk path.
- Method
- Get the configured local disk path for file storage.
- Method
- Deletes the file from local disk, if it exists.
- Method
- Read the file data off local disk.
- Method
- Write the file data to local disk. Returns the relative path as the file data handle.
- Method
- Method
- Method
- This engine identifies as "local-disk".
- Method
- Method
- Test storage engine. Does not actually store files. Used for unit tests.
- Class
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Amazon S3 file storage engine. This engine scales well but is relatively high-latency since data has to be pulled off S3.
- Class
- Create a new S3 API object.
- Method
- Retrieve the S3 bucket name.
- Method
- Delete a blob from Amazon S3.
- Method
- Load a stored blob from Amazon S3.
- Method
- Writes file data into Amazon S3.
- Method
- Method
- Method
- This engine identifies as `amazon-s3`.
- Method
- MySQL blob storage engine. This engine is the easiest to set up but doesn't scale very well.
- Class
- Load the Lisk object that stores the file data for a handle.
- Method
- Delete a blob from MySQL.
- Method
- Load a stored blob from MySQL.
- Method
- Write file data into the big blob store table in MySQL. Returns the row ID as the file data handle.
- Method
- Method
- Method
- Method
- Method
- For historical reasons, this engine identifies as "blob".
- Method
- Defines a storage engine which can write file data somewhere (like a database, local disk, Amazon S3, the A:\ drive, or a custom filer) and retrieve it later.
- Class
- Method
- Method
- Return the largest file size which can not be uploaded in chunks.
- Method
- Method
- Method
- Method
- Method
- Select viable default storage engines according to configuration. We'll select the MySQL and Local Disk storage engines if they are configured to allow a given file.
- Method
- Delete the data for a file previously written by @{method:writeFile}.
- Method
- Read the contents of a file previously written by @{method:writeFile}.
- Method
- Write file data to the backing storage and return a handle which can later be used to read or delete it. For example, if the backing storage is local disk, the handle could be the path to the file.
- Method
- Identifies chunking storage engines.
- Method
- Identifies storage engines that support unit tests.
- Method
- Return maximum storable file size, in bytes.
- Method
- Return `true` if the engine has a filesize limit on storable files.
- Method
- Return `true` if the engine is currently writable.
- Method
- Prioritize this engine relative to other engines.
- Method
- Return a unique, nonempty string which identifies this storage engine. This is used to look up the storage engine when files needs to be read or deleted. For instance, if you store files by giving them to a duck for safe keeping in his nest down by the pond, you might return 'duck' from this method.
- Method
- Construct a new storage engine.
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Find a storage engine which is suitable for storing chunks.
- Method
- Method
- Method
- Compute a chunked file hash for the viewer.
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- We can write chunks if we have at least one valid storage engine underneath us.
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method