Skip to content

Filesystems

Filesystems are a Client, but for files. They allow you to define and configure the connection to a filesystem (whether FTP, SFTP, Google Cloud, AWS, etc.) and then use that connection in your integrations.

There are a few types of Filesystems:

  • HTTP: When you've got a filesystem accesible through HTTP. Almost never used like this.
  • FTP: The most common filesystem. It's a very old protocol, but still used a lot.
  • SFTP: A more secure version of FTP. It's a bit more modern, and more secure.
  • Google Cloud Storage: Google's filesystem.
  • AWS S3: Amazon's filesystem.
  • WebDAV: A filesystem that is often used for sharing files. It's not very common, but it's still used.
  • Local Filesystem: Alumio's local filesystem. This works pretty much the same as a 'storage', so there are little usecases. A usecase would for example be if you want to store images or binary files. (Note that this filesystem does not have a 'cleaning' mechanism, so be very careful not to overload the disk)

(S)FTP Configuration

SFTP is generally preferred, because the data is encrypted. FTP & SFTP are very similar, so the configuration is very similar as well.

Generally, you have:

  • The host. That's the IP-address or the domain name of the server.
  • The port. This is generally 22 for SFTP, and 21 for FTP.
  • The username & password. This is the username & password you use to log in to the server.
  • The root directory. This is the directory where you want to start looking for files. This is generally / , but it can be different.
  • The log-leves. Generally, you'll want to DISABLE the 'log file contents', otherwise your diskspace might dissappear rapidly.