File System Transport
Digest
Technical
How to Create a File System Transport
To create a new File System Transport:
- Go to Administration > Transports
- Click New Transport on the left.
- On the Transport Type selection screen choose File System and click Submit.
- Complete the following fields in the General pane:
- System Name - The name of the Transport in Cascade.
- Parent Container - The Transport Container in which the Transport will reside.
- Server Directory - An optional directory path that is prepended to a non-absolute Destination Directory path when determining the full published path of an asset. This combined path is then prepended to asset paths when publishing. For example, if a Transport has a Server Directory of '/www/publish root', the Destination using the Transport has a Directory of 'mysite' and the asset being published has a system path of '/content/my press release'; then the asset will be published to the '/www/publish root/mysite/content' directory on the FTP/SFTP server. If, however, the Destination being used contains an absolute path, then the Server Directory field on the Transport will be ignored.
- Submit.
-
File System Access Rights and Permissions
File System Transports are restricted by file system level access rights and permissions. In order to successfully publish, the user who owns the Cascade process must have write access to the directory specified in the Transport. Otherwise, the publish report will contain access rights violations.
Mapped Network Locations
It is possible to publish to a mapped network drive using a File System Transport. The directory used as the mount point for a network-mapped drive should be treated like any other directory in the file system. Note, however, that because Cascade is treating the drive like a directory; the mechanism by which the drive is being shared (NFS, FTP, etc.) cannot be managed by Cascade. An alternative would be to set up an FTP/SFTP server and a corresponding FTP/SFTP Transport that can be managed from within Cascade.

