Child pages
  • Sakai 2.9 - Ability to host content on a separate domain
Skip to end of metadata
Go to start of metadata
Ability to host uploaded content on a separate domain
Below are the properties you'd want to set to enable this functionality:
# turns on the functionality
#content.separateDomains=true
# the FQDN of the Resources Domain in your environment.
#content.chs.serverName=files.sakaiapp.org
# the full schema and domain name for constructing URLs in your environment
#content.chs.serverUrl=http://files.sakaiapp.org
As an example, Indiana University has this setup:
8 "normal" app server nodes serving OLTP, under https://oncourse.iu.edu
3 "resource" app server nodes serving only file content, under https://resources.oncourse.iu.edu
So, our settings are these:
content.chs.serverName=resources.oncourse.iu.edu
content.chs.serverUrl=https://resources.oncourse.iu.edu
The below settings are what IU runs in production (and are the defaults), but you are welcome to change as you feel necessary.
# These are the configured defaults, so no reason to override unless you intend to change them
#content.login.urlprefixes.count = 4
#content.login.urlprefixes.1 = /access/login
#content.login.urlprefixes.2 = /sakai-login-tool
#content.login.urlprefixes.3 = /access/require
#content.login.urlprefixes.4 = /access/accept
# These are the configured defaults, so no reason to override unless you intend to change them
#content.chs.urlprefixes.count = 2
#content.chs.urlprefixes.1 = /access/
#content.chs.urlprefixes.2 = /web/
# Exceptions to the content.chs.urlprefixes patterns
# These are the configured defaults, so no reason to override unless you intend to change them
#content.chsexception.urlprefixes.count = 3
#content.chsexception.urlprefixes.1 = /access/calendar/
#content.chsexception.urlprefixes.2 = /access/citation/export_ris_sel/
#content.chsexception.urlprefixes.3 = /access/citation/export_ris_all/
  • No labels