Constellation (FileSystem) is in charge of keeping track of all directories and files on the ecosystem. In addition, it sends off the request to the module implementation to upload, clone, and delete files. The reasoning is that if we build a file structure in our service we do not need to worry about using one of the (very few) protocols that neatly keep track of files. Instead, we can simply expect a location hash or some other way to fetch the file while Warp does all the leg work for tracking and organizing the files.
The Constellation
acts similarly to a Directory
, however, it includes helpful methods to create clones, backup the
structure, import the structure, and more. It should be used to interface with Files
and Directory
as opposed to
interfacing with them directly (in most cases).
The File
is a representation of the files uploaded to the Constellation
. A File
should reference an accessible location to retrieve the file that has been uploaded.
The Directory
, much like File
, is built on top of Item
, but includes a lot more functionality than File
that
allow for storage of both File
and Directory
.
Running with IPFS for the backbone of remote storage, you can enable this native extension to automatically upload files to the IPFS ecosystem as well as remotely store your index files on a chain. Remote pinning is managed courtesy of Satellite.
More info here: IPFS Extension
Running with Storj for the backbone of remote storage, you can enable this native extension to automatically upload files to the Storj ecosystem as well as remotely store your index files on a chain. Storj includes a 150GB Free Tier which is handy for development.
More info here: Storj Extension