Configuring a shared file content workspace - Configuring a shared file content workspace - Alfresco - Alfresco Media Management - Alfresco/Alfresco-Media-Management/1.3/Alfresco-Media-Management/Alfresco-Media-Management/Configure/Configuring-a-shared-file-content-workspace - 1.3

You can configure Alfresco to use Amazon S3 or file directories for sharing content.

Configure a directory as a shared content workspace using alfresco-global.properties.

Ensure that you have installed the required external and internal software. See Prerequisites for using Media Management

1. Stop the Alfresco server.

2. Edit your alfresco-global.properties file to specify your source and target content workspace type, and the location of your source and target directories, for example:

   content.remote.default.contentRefHandler.source.type=file
   content.remote.default.contentRefHandler.source.file.dir=
   content.remote.default.contentRefHandler.target.type=file
   content.remote.default.contentRefHandler.target.file.dir=
   

   A sample alfresco-global.properties file is shipped in the root folder of the Media Management distribution zip, which defines custom properties.

3. Update your remote-node/config.yml file that you extracted from the Media Management distribution zip with your shared content workspace properties:

   transform:
       contentReferenceHandler:
           source:
               type: file
               file:
                   path: /tmp/AlfrescoContentServices
           target:
               type: file
               file:
                   path: /tmp/AlfrescoContentServices
   

   You can use the same mounted network volume directory (for example, NFS) for both the Content Services repository (configured using content.remote.default.contentRefHandler.* properties) and the remote node.

   The content services node uses ImageMagick and FFmpeg and requires that the executable directories are available on the system PATH variable or are specified in alfresco-global.properties.

   For more information about the content services framework, see Content services node architecture.

4. Start your Content Services server to apply the changes.