Book Image

Moodle 3.x Developer's Guide

By : Ian Wild, Jaswant Tak
Book Image

Moodle 3.x Developer's Guide

By: Ian Wild, Jaswant Tak

Overview of this book

The new and revamped Moodle is the top choice for developers to create cutting edge e-learning apps that cater to different user’s segments and are visually appealing as well. This book explains how the Moodle 3.x platform provides a framework that allows developers to create a customized e-learning solution. It begins with an exploration of the different types of plugin.. We then continue with an investigation of creating new courses. You will create a custom plugin that pulls in resources from a third-party repository. Then you’ll learn how users can be assigned to courses and granted the necessary permissions. Furthermore, you will develop a custom user home. At the end of the book, we’ll discuss the Web Services API to fully automate Moodle 3.x in real time.
Table of Contents (19 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
6
Managing Users - Letting in the Crowds

Committing changes


Once a change to the code is made, we will need to commit them both into our local repository and to GitHub. Ensure that Git Bash is set to the correct working directory. Once the directory is correct, type git status to check what changes have been made locally in Git Bash:

Determine the changes that have been implemented in each file using the git diff command:

Lines that have been added are shown in green and prefixed with a "+". Those lines which have been removed are shown in red and prefixed with a "-".

To commit a change, use the git commit command:

Remember to include a comment using the -m switch.

Once all of your changes have been committed to your local repository, you need to push them up to GitHub using the git push command:

Your latest changes will be visible in GitHub, as follows:

Atomised commits

Rather than committing a number of different changes to a repository in one commit, it is far better to apply one commit per change. This technique ensures that it is...