-
Notifications
You must be signed in to change notification settings - Fork 0
Moodle Admin Handbook
VMChecker Next is a block type plugin for Moodle, as such the instalation directory of this plugin is <moodle_root>/blocks/
. The name of the from Moodle's perspective is and the sources of this plugin must reside in <moodle_root>/blocks/vmchecker
.
Currently, the plugin can only be downloaded from Github, with the prospect of adding it to the Moodle plugin repository.
The source code for the plugin can be found at vmchecker-next. Simply download the archive with the source code (go to Code -> Download ZIP).
As an Admin user go to Site Administration -> Plugins -> Install plugins. Upload the archive with the source files and press Install plugin from the ZIP file
. A summary page will be presented, which on successful validation of the arhcive will allow you to install the plugin. Simply click continue and then follow the steps described in the Plugin configuration section.
Simply extract the archive in a tmp folder and rename the extracted folder to vmchecker
.
unzip vmchecker-next.zip /tmp
mv /tmp/vmchecker-next /tmp/vmchecker
Now, move the source folder to the moodle instalation directory inside the blocks
subfolder.
mv /tmp/vmchecker "${moodle_root_folder}/blocks"
After the plugin sources are added, on the next login of the admin user, a prompt, asking if you want to install the new plugin, will appear. Next, you will be asked to upgrade the database, the Admin user will be asked to configure the newly installed vmchecker plugin.
Currently there are 2 configurations that must be setup:
-
vmck backend - The backend URL, to which requests for checking submissions are made. Currently it should be set to
http://141.85.224.199:8000/api/v1/
-
Submissions check count - It indicates how many submissions should be checked on each cron call. This is to make sure that the checking of submissions does not take longer than a minute (the usual cron interval). The default value is
50
, but it can be lowered if there are valid conerns of the plugin acaparating then entire cron job (it is left to the discretion of the admin).