udir-moodle/mod_scheduler

Scheduler — Composer/Packagist mirror of the Moodle plugin mod_scheduler, auto-updated from the Moodle plugins directory.

2023052300 2026-06-16 16:54 UTC

Requires

• composer/installers: ~1.0 || ~2.0
• moodle/moodle: 4.0.* || 4.1.* || 4.2.*

GPL-3.0-or-later

README

This repository is a Composer/Packagist mirror of the Moodle plugin mod_scheduler. The plugin's own files live at the repository root; a daily GitHub Action advances to the next published version and tags it, so Packagist always tracks the directory.

Package	udir-moodle/mod_scheduler (type moodle-mod)
Installs to	the Moodle path for that type, via composer/installers (folder scheduler)
Tags	the Moodle $plugin->version integer (e.g. 2024100700), one per release
Updater	goupdate (config: .goupdate.yml), run by .github/workflows/update.yml daily
Compatibility	each release requires moodle/moodle matching the Moodle versions it supports

Only this .github/ folder, composer.json, and .goupdate.yml are owned by the mirror — they always survive an update; everything else is the upstream plugin and is replaced.

Setup in your Moodle/Composer project (required)

Each release requires moodle/moodle (the official core package — Packagist mirrors the github.com/moodle/moodle tags), so declare your core version first and bump it when you upgrade Moodle:

// composer.json of your site — pick ONE:
"require": { "moodle/moodle": "4.5.10" }    // installs core source, unused, into vendor/moodle/moodle
"replace": { "moodle/moodle": "4.5.10" }    // core already lives in your repo — declare without installing

composer require 'udir-moodle/mod_scheduler:*'   # '*' — versions are Moodle date integers

Composer then never selects a release that doesn't support your Moodle, and upgrading core pulls plugins forward. If you skip the declaration, composer satisfies the requirement itself by installing whatever core version fits into vendor/ — declare it so updates are gated to your Moodle.

Custom placement

composer/installers installs moodle-mod packages to their standard Moodle path automatically. To place differently, the consuming project's composer.json decides:

"extra": { "installer-paths": {
    "custom/path/{$name}/": ["type:moodle-mod"],           // every moodle-mod package
    "exact/dir/":           ["udir-moodle/mod_scheduler"]  // only this package
} }

If moodle-mod is a sub-plugin type composer/installers doesn't know, also require oomphinc/composer-installers-extender and add "installer-types": ["moodle-mod"].

Generated by moodle-composer-toolkit — see its README for setup and Packagist registration.