Skin Manager Installation

The Sakai Skin manager comes as source distribution.

Prerequisites

This manual assumes that you are familiar with installing, building, and running Sakai. You must be familiar with the concepts in the Sakai installation guide, which can be found at the Sakai Release Documentation.

Of course, you need a Sakai installation to use this Sakai tool.

Installing from source

Downloading the source

The source can be found at https://github.com/EdiaEducationTechnology/edia-sakai-skinmanager

Building the source

The source can be build with the following command, replace SAKAI_HOME with the Sakai installation directory.

mvn clean install sakai:deploy -Dmaven.tomcat.home=<SAKAI_HOME>

Database

Database support

database installation

The Sakai skin manager makes use of one table, which is mapped by hibernate. Sakai needs to be started with the

auto.ddl=true

set in the sakai.properties on the first run of the skin manager to let hibernate create the required table for you.

Enable full skin management

Since version 4.2 the skin manager has the ability to take full control over the skin management. This feature will overwrite skins that are deployed by the library.war file. This comes in handy when the library.war file gets redeployed on an update.

# The interval to sync the skin directory
skinmanager.sync.interval=30000
# Set to true of the skin sync should run forever, false to just run the sync at startup
skinmanager.sync.continious=true
# The time interval to wait for redeployment.
skinmanager.deploy.wait=10000
# If set to true, the skinmanager will overwrite the the skin on the filesystem if there is a skin archive available, also of the skin on the filesystem is newer.
skinmanager.deploy.overwrite=true