Page Comparison

...

Some Sakai tools use custom paths to store assets in the file system, outside the ContentHostingService. Each case will have to to be addressed accordingly.

• Samigo (Some 2.2 release notes remark on this topic)
  • Pre-2.2 Samigo can be configured to store content in either the database, which is not recommended by the Samigo team, or in the file system. In reality, the non-DB option simply removes the 2nd of a two-part process for file uploading:
    • files are uploaded to the systems configtured temp directory (/tmp in linux). ref's to those files are functional
    • if DB storage is enable, those files are then moved to the DB and ref's are updated
  • the following refers to 2.2 but may also apply to prior versions:
    • for general questionType media, sakai.properties has

      Code Block
      samigo.answerUploadRepositoryPath=/sakaitmp/ samigo.sizeThreshold=512 samigo.sizeMax=20480 samigo.saveMediaToDb=false

    • for QTI imports, the com.corejsf.UploadFilter.repositoryPath parameter in web.xml is set to /tmp by default and can be overridden in the sakai.properties file as well:

      Code Block
      samigo.answerUploadRepositoryPath=/sakaitmp/

• Melete
  • Melete uses a propertie to confiure the file system location for documents. However in pre-2.2, this configuration does not appear to be functional. The assumed location is in /var

...