The delivery process follows a 4-step logic:
The version currently in service must be synchronised with a temporary “security” version that will continue to be executed until the delivery preparation is complete. The synchronisation tool manages two copies:
Component path: Partial synchronisations can be done on a single part of the Moodle code base by entering a relative path here (for example: 'mod' will only synchronise the activity modules directory).
The Moodle service continues to be provided from the temporary secured version. This version remains stable throughout the phase of modification and update of the production version's Moodle code.
Use these tools to trigger the file update commands according to the versioning tool chosen in the configuration.
You can perform several successive partial updates by entering a relative path to a specific component or tree.
This is the most delicate operation, because you push the newly delivered code into production.
The delivery operation will certainly require you to perform the Moodle logical updates (Administration > Notifications)
Malfunctions may then appear, mainly following:
This code can lead to changes in the data structures in the database, sometimes irreversibly (the changes made are no longer backward compatible with the old Moodle PHP code). This situation remains rare, however.
Back to the user guide - Back to the component index- plugins index -Back to the catalogue