Ticket::Article::Backend::MIMEBase::ArticleDataDir
Specifies the directory to store the data in, if “FS” was selected for ArticleStorage.
This setting can not be deactivated.
Default value:
<OTRS_CONFIG_Home>/var/article
Ticket::Article::Backend::MIMEBase::ArticleStorage
Defines how to store the article files and the attachments of the articles. You can switch between the modules even on a system that is already in production without any loss of data.
Available in-built options:
-
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB: The article files and attachments are stored completely in the database (not recommended for storing big attachments). -
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageFS: The article files and attachments are stored in the filesystem. This is faster but the webserver should run under the OTRS user. -
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageAmazonS3: The article files and attachments are stored on an file storage service (like Amazon S3). This is very useful for distributed and loadbalanced systems.
Note: Searching for attachment names is not supported when “FS” is used.
This setting can not be deactivated.
Default value:
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB
Ticket::Article::Backend::MIMEBase::ArticleStorageBackendCheckOrder
Defines which storage backends additionally should be checked for articles. The order of the entries in the list defines the order which backend is checked first. This is only required for installations where articles are stored in different storage backends.
This setting can not be deactivated.
Default value:
--- []
Ticket::Article::Backend::MIMEBase::IndexAttachmentNames
Specifies whether the (MIMEBase) article attachments will be indexed and searchable.
This setting can not be deactivated.
Default value:
1
