Project
Sakai Deployment and Customization
Deployment automation and tenant branding for the upstream Sakai LMS, with Docker scripts and Java patches.
How it’s builtHow it’s built
Sakai Deployment and Customization · Dockerised Sakai 23 deployment with multi-tenant branding and a custom faculty hierarchy tool
This work packages the upstream Sakai 23 LMS for repeatable deployment and adapts it for multiple universities on aflon.com.ng. I built a multi-stage Docker image that compiles Sakai with Maven onto Tomcat 9, a manage.sh CLI with 16 commands, and Nginx configs for 7 sites. In sakai-project-dev I patched the login tool so each tenant host gets its own skin and title, and added a Faculties tool (8 Java classes, 6 Velocity views) for faculty, department, level and semester browsing.
- manage.sh commands
- 16
- configured tenants
- 2
- files in the custom Faculties tool
- 18
- Nginx site configs
- 7
- commits in sakai-project-dev, all mine
- 26
Technology and what it does here
- Sakai 23.x (Java)
- Upstream LMS cloned and built from the 23.x branch
- Docker multi-stage build
- Maven:3.9-eclipse-temurin-11 builder then tomcat:9.0-jdk11 runtime
- Docker Compose + MySQL 8.0
- Db and sakai services with persistent volumes
- Maven
- Mvn clean install sakai:deploy into Tomcat
- Tomcat 9
- Servlet container; custom server.xml, UTF-8 connector, 2 GB heap
- Nginx
- Reverse proxy and TLS for Sakai and tenant subdomains
- Velocity templates
- Views for the Faculties hierarchy tool
- Bash
- Install, start/stop, multitenancy setup, patch application, DB backup scripts
Implementation details
- The login patch resolves skin.default.<tenant> and ui.service.<tenant> from the request host or an X-Sakai-Tenant header.
- A Faculties tool with Faculty, Department, Level, Semester, Course and CourseMaterial models serves a browsable academic hierarchy.
- The image builds Sakai from source in a builder stage and ships only the deployed artefacts on Tomcat.
Technologies
- Sakai
- Docker
- Java
