This first group of settings configures the delivery tools themselves. A version of these tools is available in the component's 'prodscripts' directory and can be used directly from there.

In general, for obvious security reasons, it is preferable to move these tools out of the Moodle tree and install them elsewhere on the system. Note that while they run, a complete copy of the Moodle code base is produced (once or twice) to secure the delivery process. Operating these tools from their original location could present risks of recursive copying of the Moodle directory. See the installation section for more information. Delivery method

In each case, the respective system commands must be installed on the server.

For cvs, on Linux:

 apt-get install cvs-client

For svn, on Linux:

 apt-get install subversion

Designates the path to the delivery tools. If the path is “real”, it must point to the exact directory where the toolset is installed. Otherwise it must point to the “prodscripts” directory mentioned above.

To operate, the tools must be able to point to a local directory containing the production Moodle code base to manage. This directory will be a symbolic link if this Moodle's service is located elsewhere on the system.

If for example your setup is as follows:

Moodle location: /var/www/mymoodle

Remote tools location: /var/prodscripts/mymoodletools

the content of the mymoodletools directory:

-rwxrwx— goback … lrwxrwxrwx mymoodle → /var/www/mymoodle drwxrwxr-x mymoodle-SAVE drwxrwxr-x mymoodle-SUPERSAVE

then the value of this parameter is: mymoodle

If the tools are deployed directly in the “Path to the tools” directory, then this box must be ticked. If it is not, Moodle uses the tools of the distribution by appending the configured distribution method to the path.

Back to the component index - components index -Back to catalogue