Remote file systems support is in preview mode. Most functionality is available, but bugs are possible.
Supported file systems
In F2 Commander, a “file system” can be anything that can seem to contain files and directories, (a local disk, a BLOB storage, a Cloud drive, a compressed file, etc.).
A non-exhaustive list of supported file systems includes: AWS S3, GCP GCS, Azure ADLS, OCI, OSS, DVC, LakeFS, HDFS, Dropbox, Google Drive, FTP/FTPS, SFTP, SMB, WebDAV, and many more.
In practice, “file system” support is provided by fsspec and its implementations. It means that more implementations than those mentioned above may be available, as long as an according Python package is installed alongside F2 Commander in the same Pyhton environment, and assuming that F2 Commander can handle it’s initialization (more on it below).
Connecting to a remote file system
To connect to a remote file system, open the “Connect” dialog with Ctrl+t.
“Connect” dialog, exposes the underlying connector configuration: you will be presented with all possible connection options. These options depend on the implementation of the file system connector. You may need to refer to the documentation of the installed additional packages for more information.
For example, see the fsspec built-in implementations documentation.
To connect to some remote file systems you may need to install additional packages. The names of the missing packages are indicated in the “Connect” dialog upon selecting a protocol.
For example, if you installed F2 Commander with pipx, and you want to connect
to an S3 bucket, you need to install the s3fs package:
pipx inject f2-commander s3fs
Remote file systems bookmarks
It is possible to persist a connection for a remote file system, to quickly reconnect to it without using the connection dialog. See the “Remote file systems” section in the Configuration