App Storage Location

Rocket.Chat's version 4 introduced npm packages as dependencies of apps. Since npm dependencies could account for a hefty portion of an app package's final size, we have a more flexible storage solution for your apps' packages.

To access the configuration, go to Administration > Workspace > Settings > General > Apps.

The settings are as follows:

• Number of days to keep logs from apps stored: Select the number of days that you want to store the app logs. The options are 7 days, 14 days, and 30 days. Note that depending on the size of the logs collection, changing this setting may cause slowness for some moments.

• Apps' Source Package Storage type: Currently, we have two storage methods, GridFS at MongoDB (the default option) and Filesystem at the host's box.

  • GridFS: When using GridFS (default), your app package is stored in the database as a file, and you don't have to manage configuration to make it work.

  • Filesystem: When setting the storage to the filesystem, you have full control of the package's storage location and access control. There are a few requirements to make it work.

    • You must provide the absolute path of the directory where the packages will be stored in the configuration.

    • The Rocket.Chat server must have read and write permissions to the path so it can manage the packages.

• Directory for storing apps source package: If you select Filesystem as the app source storage type, enter the absolute path in the filesystem for storing the apps' source code (in .zip file format).

It is not recommended to change storage configuration when apps are installed. Currently, there is no migration mechanism to move packages between different storage methods. Doing so will result in apps not working properly.