{"_id":"5a2a8b1ce25025003c5829f9","project":"55faf11ba62ba1170021a9a7","version":{"_id":"55faf11ba62ba1170021a9aa","project":"55faf11ba62ba1170021a9a7","__v":40,"createdAt":"2015-09-17T16:58:03.490Z","releaseDate":"2015-09-17T16:58:03.490Z","categories":["55faf11ca62ba1170021a9ab","55faf8f4d0e22017005b8272","55faf91aa62ba1170021a9b5","55faf929a8a7770d00c2c0bd","55faf932a8a7770d00c2c0bf","55faf94b17b9d00d00969f47","55faf958d0e22017005b8274","55faf95fa8a7770d00c2c0c0","55faf96917b9d00d00969f48","55faf970a8a7770d00c2c0c1","55faf98c825d5f19001fa3a6","55faf99aa62ba1170021a9b8","55faf99fa62ba1170021a9b9","55faf9aa17b9d00d00969f49","55faf9b6a8a7770d00c2c0c3","55faf9bda62ba1170021a9ba","5604570090ee490d00440551","5637e8b2fbe1c50d008cb078","5649bb624fa1460d00780add","5671974d1b6b730d008b4823","5671979d60c8e70d006c9760","568e8eef70ca1f0d0035808e","56d0a2081ecc471500f1795e","56d4a0adde40c70b00823ea3","56d96b03dd90610b00270849","56fbb83d8f21c817002af880","573c811bee2b3b2200422be1","576bc92afb62dd20001cda85","5771811e27a5c20e00030dcd","5785191af3a10c0e009b75b0","57bdf84d5d48411900cd8dc0","57ff5c5dc135231700aed806","5804caf792398f0f00e77521","58458b4fba4f1c0f009692bb","586d3c287c6b5b2300c05055","58ef66d88646742f009a0216","58f5d52d7891630f00fe4e77","59a555bccdbd85001bfb1442","5a2a81f688574d001e9934f5","5b080c8d7833b20003ddbb6f"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"5a2a81f688574d001e9934f5","project":"55faf11ba62ba1170021a9a7","version":"55faf11ba62ba1170021a9aa","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-12-08T12:13:42.092Z","from_sync":false,"order":36,"slug":"sbfs-command-reference","title":"SBFS Command Reference"},"user":"566590c83889610d0008a253","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-12-08T12:52:44.770Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"##Overview\n\nLearn about the actions available with SBFS once your project has been mounted. Each action's availability in `read-write` and `read-only` modes is specified.\n\nNotes describe certain behaviors of the actions where applicable. Since there are multiple ways to perform these actions, such as via the command line interface or another application, the actual methods for these actions will not be described. \n\n##List a directory\n\n`read-write: Available`\n`read-only: Available`\n\n##Create a file\n\n`read-write: Available`\n`read-only: Available`\n\n##Write a file\n`read-write: Available`\n`read-only: Not available`\n\nWrite to a file after it has been created but before it is closed. Only sequential write is supported. Once the file is closed, it becomes immutable. \n\n##Execute a file\n`read-write: Available`\n`read-only: Not available`\n\nYou need to have execute permissions on a particular file to perform this action. The [permissions are set ](doc:mount) during when the file is mounted. \n\n##Delete a file\n`read-write: Available`\n`read-only: Not available`\n\nRemoving a file from a mounted file system also removes that file from the Platform project. This action is irreversible. \n\n##Move a file from a mounted directory to a local file system\n`read-write: Available`\n`read-only: Not available`\n\nThis is equivalent to downloading a file to a local file system and removing it from the mounted file system. Moving a file from the mounted file system also removes that file from the Platform project. This action is irreversible.\n\n##Move a file from a local file system into a mounted directory\n`read-write: Available`\n`read-only: Not available`\n\nThis is equivalent to uploading a file to the Platform. Moving the file into the mounted file system sets file access permissions in accordance with the mounted file system.\n\n##Move a file inside of the mounted file system into another directory\n`read-write: Available`\n`read-only: Not available`\n\nMove the file data along with its metadata. \n\n##Rename a file\n`read-write: Available`\n`read-only: Not available`\n\n##Copy a file from a mounted directory to a local file system \n`read-write: Available`\n`read-only: Available`\n\nThis is equivalent to downloading a file from the Platform to a local file system. \n\n##Copy a file into a mounted directory\n`read-write: Available`\n`read-only: Not available`\n\nCopying a file into the mounted file system [sets file access permission](doc:mount) in accordance with the mounted file system. \n\n##Copy a file inside of the mounted directory\n`read-write: Available`\n`read-only: Not available`\n\nCopying a file inside a mounted directory is effectively the same as downloading and subsequently uploading the file. Note that metadata is not copied when performing this operation. Also, consider using hard links instead of copying the file. \n\n##Create a hard link between a mounted and local file system\n`read-write: Available`\n`read-only: Not available`\n \nCreating a hard link inside a mounted file system is effectively the same as copying a file in that a new file is created with the same content and metadata as the original file. However, the subsequent removal of the original (source) file does not affect the linked file.\n \n##Create a symbolic link on a local file system to a mounted file\n`read-write: Available`\n`read-only: Available`\n\nNote that unmounting the file system results in a broken link. However, subsequent mounting of the same project to the same mountpoint renders the link valid once more. \n\n##Create a symbolic link inside of the mounted file system\n`read-write: Available`\n`read-only: Not available`\n\nThe created symbolic link is ephemeral, meaning that it is removed after unmounting the file system mounted via SBFS. The symbolic link is created only in the mounted file system is not visible via the Platform's visual interface or via the API.  \n\n##Create a directory\n`read-write: Available`\n`read-only: Not available`\n\n##Move a directory from the mounted file system\n`read-write: Available`\n`read-only: Not available`\n\nMoving a directory out from a mounted file system removes the directory itself and the files within from the Platform project. This action is irreversible. \n\n##Move a directory into a mounted file system\n`read-write: Available`\n`read-only: Not available`\n\n##Delete a directory\n`read-write: Available`\n`read-only: Not available`\n\nRemoving a directory from the mounted file system removes the directory itself and the files within from the Platform project. This action is irreversible. \n\n##Unavailable actions\nThe following common actions are not available:\n\n  * Edit a file\n  * Rename a directory\n  * Change permissions on a file or a directory (`chmod`) (Setting permissions on files is possible only at the time of mounting. Alterations are not permitted at a later time.)\n  * Change ownership of a file or a directory (`chown`)","excerpt":"","slug":"actions-after-mounting","type":"basic","title":"Actions after mounting"}

Actions after mounting


##Overview Learn about the actions available with SBFS once your project has been mounted. Each action's availability in `read-write` and `read-only` modes is specified. Notes describe certain behaviors of the actions where applicable. Since there are multiple ways to perform these actions, such as via the command line interface or another application, the actual methods for these actions will not be described. ##List a directory `read-write: Available` `read-only: Available` ##Create a file `read-write: Available` `read-only: Available` ##Write a file `read-write: Available` `read-only: Not available` Write to a file after it has been created but before it is closed. Only sequential write is supported. Once the file is closed, it becomes immutable. ##Execute a file `read-write: Available` `read-only: Not available` You need to have execute permissions on a particular file to perform this action. The [permissions are set ](doc:mount) during when the file is mounted. ##Delete a file `read-write: Available` `read-only: Not available` Removing a file from a mounted file system also removes that file from the Platform project. This action is irreversible. ##Move a file from a mounted directory to a local file system `read-write: Available` `read-only: Not available` This is equivalent to downloading a file to a local file system and removing it from the mounted file system. Moving a file from the mounted file system also removes that file from the Platform project. This action is irreversible. ##Move a file from a local file system into a mounted directory `read-write: Available` `read-only: Not available` This is equivalent to uploading a file to the Platform. Moving the file into the mounted file system sets file access permissions in accordance with the mounted file system. ##Move a file inside of the mounted file system into another directory `read-write: Available` `read-only: Not available` Move the file data along with its metadata. ##Rename a file `read-write: Available` `read-only: Not available` ##Copy a file from a mounted directory to a local file system `read-write: Available` `read-only: Available` This is equivalent to downloading a file from the Platform to a local file system. ##Copy a file into a mounted directory `read-write: Available` `read-only: Not available` Copying a file into the mounted file system [sets file access permission](doc:mount) in accordance with the mounted file system. ##Copy a file inside of the mounted directory `read-write: Available` `read-only: Not available` Copying a file inside a mounted directory is effectively the same as downloading and subsequently uploading the file. Note that metadata is not copied when performing this operation. Also, consider using hard links instead of copying the file. ##Create a hard link between a mounted and local file system `read-write: Available` `read-only: Not available` Creating a hard link inside a mounted file system is effectively the same as copying a file in that a new file is created with the same content and metadata as the original file. However, the subsequent removal of the original (source) file does not affect the linked file. ##Create a symbolic link on a local file system to a mounted file `read-write: Available` `read-only: Available` Note that unmounting the file system results in a broken link. However, subsequent mounting of the same project to the same mountpoint renders the link valid once more. ##Create a symbolic link inside of the mounted file system `read-write: Available` `read-only: Not available` The created symbolic link is ephemeral, meaning that it is removed after unmounting the file system mounted via SBFS. The symbolic link is created only in the mounted file system is not visible via the Platform's visual interface or via the API. ##Create a directory `read-write: Available` `read-only: Not available` ##Move a directory from the mounted file system `read-write: Available` `read-only: Not available` Moving a directory out from a mounted file system removes the directory itself and the files within from the Platform project. This action is irreversible. ##Move a directory into a mounted file system `read-write: Available` `read-only: Not available` ##Delete a directory `read-write: Available` `read-only: Not available` Removing a directory from the mounted file system removes the directory itself and the files within from the Platform project. This action is irreversible. ##Unavailable actions The following common actions are not available: * Edit a file * Rename a directory * Change permissions on a file or a directory (`chmod`) (Setting permissions on files is possible only at the time of mounting. Alterations are not permitted at a later time.) * Change ownership of a file or a directory (`chown`)