File System Deployment Handler

Handles the deployment of one or more Deployment Packages to a file system.

A file system is described by a local path on disk, such as:

/www/files
/data
/Users/joesmith/files

These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage).

The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated.

Nodes are written to disk like this:

{deploymentPath}/{nodeId}/node.json

Node attachments are written as well, like this:

{deploymentPath}/{nodeId}/attachments/{attachmentId}.{ext}

Associations are written to disk like this:

{deploymentPath}/{associationId}/association.json

Association attachments are written as well, like this:

{deploymentPath}/{associationId}/attachments/{attachmentId}.{ext}

Configuration

{
    "deploymentPath": "{deploymentPath}"
}

Where deploymentPath is the file path on disk.

Example

{
    "deploymentPath": "/www/files"
}