package example.com 01ed8bb7a8ad5500c8885da1575f77068d0777606d
..are resolved relative to the
/sys/packagesfile. For example, the type
gallery.boomla.net/gallerywould resolve to
A fileNodeId is a unique identifier for a file within a volume. When a file is moved within the same volume, its fileNodeId won't change.
A filesystem is a tree of one or more volumes.
The filesystem interface version defines the filesystem schema and any additional behavior on how the Boomla OS shall treat the filesystem / website in context.
Each filesystem scope defines its own filesystem interface version.
The filesystem scope specifies the root file to be used for path resolutions. Filesystem scopes are implicitly created by some of the file link types. Filesystem scopes always start at volume roots. A filesystem scope may be local or global.
Filesystem scopes are used within packages to resolve file links and file types correctly.
The IDE is an Integrated Development Environment which can be installed on any Boomla website as a package. It provides a filesystem navigation tool and an editor for code, file properties and file attributes.
..) of a package root file does not exist when respecting the filesystem scope. It does exist when the filesystem scope is ignored.
|Link type||Static / Dynamic||Transparent||Filesystem scope||Mounts volume|
The Posix bridge is a 2-way mapping between the Boomla filesystem and Posix filesystems. Posix filesystems in this context include Windows, Mac and Linux filesystems.
The Posix bridge allows one to use programs that understand Posix filesystems to manipulate Boomla files.
~.json. It stores file properties and attributes.
.Requestis reserved for request method files.
.Request. System filenames can only be used if they are among the reserved filenames.
volumelink is a transparent link, while a
pathlink is not.