Imports an archive stored outside the polyPod into the Feature's virtual file system.
The URL of the archive to import.
The desired destination ID the imported archive's contents in the virtual file system. Will be generated if not specified.
The ID of the imported archive's contents - same as destId if
specified.
Reads the directory at the given ID recursively and returns all entries.
The ID of the directory to read.
A list of all entries within the supplied directory.
Reads the file with the given id.
The ID of the file to read.
The contents of the file.
Removes a previously imported archive.
The ID of the archive to be removed.
A promise that resolves to a value of type void.
Returns information about a file or directory.
The ID of the file or directory to analyze.
Information about the file or directory.
Writes the supplied content to the file at id.
The ID of the file to write to.
The content to write to the file.
Generated using TypeDoc
PolyOut, mysteriously named for historical reasons, allows Features to store data on a virtual file system not accessible to other Features.The API is loosely modelled after a subset of Node.js' fsPromises, with some polyPod specific functionality on top.
Instead of POSIX paths,
PolyOutdeals with IDs - platform-specific, unambiguous references to files and directories. On some platforms, these may be POSIX paths, but it could also be URLs or file handles. Manipulating IDs directly is therefore discouraged.PolyIn for access to the polyPod's internal triplestore, which is the recommended way of storing most data.