Book Image

Moodle 4 Administration - Fourth Edition

By : Alex Büchner
5 (1)
Book Image

Moodle 4 Administration - Fourth Edition

5 (1)
By: Alex Büchner

Overview of this book

This updated fourth edition of the classic Moodle Administration guide has been written from the ground up and covers all the new Moodle features in great breadth and depth. The topics have also been augmented with professional diagrams, illustrations, and checklists. The book starts by covering basic tasks such as how to set up and configure Moodle and perform day-to-day administration activities. You’ll then progress to more advanced topics that show you how to customize and extend Moodle, manage authentication and enrolments, and work with roles and capabilities. Next, you'll learn how to configure pedagogical and technical Moodle plugins and ensure your LMS complies with data protection regulations. Then, you will learn how to tighten Moodle’s security, improve its performance, and configure backup and restore procedures. Finally, you'll gain insights on how to compile custom reports, configure learning analytics, enable mobile learning, integrate Moodle via web services, and support different types of multi-tenancy. By the end of this book, you’ll be able to set up an efficient, fully fledged, and secure Moodle system.
Table of Contents (24 chapters)

Supporting multi-tenancy via a centralized code base

The principal idea of this multi-tenancy approach is to have a single code base but multiple separate and standalone Moodle instances.

An example where this kind of model is suitable is where each tenant represents a school or college in the region, and each school or college has its own Moodle admin, theme, and administration settings for managing users, courses, privacy, and grades.

The following diagram illustrates this federated approach:

Figure 20.5 – Multi-tenancy via a centralised code base

This solution requires two main configuration steps:

  1. Web server configuration:

For each Moodle instance, a separate virtual host is required where the ServerName, ErrorLog, and CustomLog parameters point to the individual instances (tenants), but the DocumentRoot variable must be identical in all virtual hosts, ensuring that the same code base (CFG->dirroot) is used. A virtual host...