diff --git a/data/academycourses.json b/data/academycourses.json index eb5732c5bb..fb0585ebcf 100644 --- a/data/academycourses.json +++ b/data/academycourses.json @@ -106,6 +106,18 @@ "series": [ "intermediate" ] + }, + "mdk": { + "id": 171, + "name": "Working with Moodle Development Kit (MDK)", + "summary": "Get to know how to use MDK to streamline your Moodle development processes", + "description": "This intermediate level course for developers is designed to help you fully leverage the Moodle Development Kit (MDK) to boost development efficiency, minimise manual tasks, enforce best practices in plugin creation, and establish more consistent Moodle development workflows both individually and collaboratively within a team.", + "tags": [ + "development", + "tools" + ], + "archived": false, + "series": [] } } } diff --git a/general/development/tools/mdk.md b/general/development/tools/mdk.md index 34f10ea91b..c5ec57ea06 100644 --- a/general/development/tools/mdk.md +++ b/general/development/tools/mdk.md @@ -10,6 +10,11 @@ Every developer creates simple tools to avoid repeating cumbersome and/or boring The most important concept of MDK is that it works with Moodle instances. An instance of Moodle is a directory in which you have checked out a particular version together with a database using a specific database engine. This means that if you want to work on Moodle 4.3 and 4.2, using both MySQL and PostgreSQL, you will have four separate instance directories. This choice was made because it is the safest, clearest, and most straightforward solution. + + ## Typical workflows using MDK To discover what MDK can do for you, here are a few common tasks it can achieve. More on [MDK's wiki](https://github.com/FMCorz/mdk/wiki/Typical-workflows). @@ -237,6 +242,7 @@ You may need to set the path variable to null: mdk config set path "" ``` +During the installation, a `.moodle-sdk` folder will be created containing a `config.json` file will. You can edit it to change your settings easily. ::: ## Upgrading MDK