Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ref: http://bugs.sakaiproject.org/confluence/display/FAQ/2.2.7.1+Configuration

This The content below is taken from bugs.sakaiproject.org/confluence:

No Format

The best place for configuring this is the sakai.properties file.

...

No Format



# the file system root for content hosting's external stored files (default is null, i.e. store them in the db)
bodyPath@org.sakaiproject.service.legacy.content.ContentHostingService =${sakai.home}content


Enable the above line, and point at the root folder for the files to be stored.

...

No Format



# when storing content hosting's body bits in files, an optional set of folders just within the content.filesystem.root

# to act as volumes to distribute the files among - a comma separate list of folders.  If left out, no volumes will be used.
bodyVolumes@org.sakaiproject.service.legacy.content.ContentHostingService = v1,v2,v3


Enable the above line, and set the list of "volumes" for storage.  You can specify one or more volume names, comma separated on this line.  These are folders under the file system root.  Files will be distributed among these volumes.

...



If you are going to use multiple volume devices, you need to map them to these volume names that live "under" the root.  We have done this with our AFS file storage system at the University of Michigan.  If you are not using separate devices, then you can use any folder names for the volumes.  Provide at least one.

...



Files will be stored under each volume in a way so that there are not too many in any one folder.  The folder structure we use is:

...



{{YYYY/DDD/HH/id, where YYYY=year, DDD=day of year, HH=hour of day, and the 1111...=an id-based file name

...

}}

for example,

...



{{2005/070/03/3223479379834-2343

...

}}

or, using the above root and volumes, it might be:

...



{{/usr/local/tomcat/sakai/content/v2/2005/070/03/3223479379834-2343

...

}}

Note that the resource name and type is not at all encoded here.  The date/time used to form the file name is the date/time of file creation.

Proposed solution(s)

a. user's space

...