BrickFTP vs. POSIX-based Filesystems
The following are some key differences between BrickFTP and POSIX-based filesystems that are important to be aware of.
Permissions in BrickFTP are entirely different from those in a typical POSIX-based filesystem. Please see our documentation on Permissions to understand how permissions work in BrickFTP.
File Modification Times
By default, file modification times are not user-settable in BrickFTP, as this can be a security concern. However, it may be beneficial for an application that needs the modified date for file synchronization. If you wish to enable user-provided modified times in BrickFTP, you can adjust the setting at Settings > General > File “last modified date” semantics. Showing the user-provided date will affect FTP, SFTP, WebDav and the web interface.
Hard Links and Symbolic Links
In POSIX-based filesystems, you can create pointers to files via hard links or symbolic links. Since BrickFTP does not use an underlying POSIX filesystem, we do not currently support either hard links or symbolic links.
With a POSIX-based filesystem, a move or copy operation can be destructive, overwriting an existing file if the destination already exists. By contrast, in BrickFTP such operations will fail if the destination already exists, preventing the existing file from being overwritten.
Note that a file must be uploaded to BrickFTP completely before the file will be available to download. Attempts to download a file before the upload has completed will fail as if the file does not exist. If an existing file is being changed, downloading it during a change will result in the previous, unchanged version of the file being downloaded.