Mimetype definition deployments - Mimetype definition deployments - Alfresco - Alfresco Transform Service - Alfresco/Alfresco-Transform-Service/1.5/Alfresco-Transform-Service/Alfresco-Transform-Service/Configure/Repository-specific-configuration/Deploying-configurations/Mimetype-definition-deployments - 1.5

Alfresco Transform Service

Platform
Alfresco
Product
Alfresco Transform Service
Release
1.5
ft:lastPublication
2026-05-06T19:55:27.734000
ft:locale
en-US
ArchiveStatus
Archived

Just like Pipeline and Rendition Definitions, custom Mimetype Definitions need to be placed in a directory of the Repository. There are similar properties that control where and when these definitions are read, and the same approach may be taken to get them into Docker Compose and Kubernetes environments.

mimetype.config.dir=shared/classes/alfresco/extension/mimetypes
mimetype.config.cronExpression=0 30 0/1 * * ?
mimetype.config.initialAndOnError.cronExpression=0/10 * * * * ?

In a Kubernetes environment:

kubectl create configmap custom-mimetype-config --from-file=custom-mimetypes.json

The necessary volumes are already provided out of the box and the files in ConfigMap custom-mimetype-config will be mounted to /usr/local/tomcat/shared/classes/alfresco/extension/mimetypes. Again, the files will be picked up the next time the location is read, or when the repository pods are restarted.