geoffreyvanwyk / ansible-role-moodle Goto Github PK

This falls under the 8. FORCED SETTINGS section of config.php.

By default, the file system is used for storing sessions in the moodledata directory. The Moodle role must provide an option for using Redis. This can be done with a role variable moodle_session_cache limited to values:

• file
• redis

The default value should be file.

References:

1. https://docs.moodle.org/402/en/Session_handling#File_session_driver
2. https://docs.moodle.org/402/en/Session_handling#Redis_session_driver

Each supported Moodle version should also be tested, because steps for their installation might differ, e.g. see #26.

Resolved by #25

The write permission is necessary for the site administrator to be able to install plugins.

Rename the "Lint" job (that does YAML Lint) to "YAML Lint".

The Ansible Lint job should depend on YAML Lint.

The Molecule job should depend on Ansible Lint.

Of the Moodle versions supported by this Ansible role, the "unrecognized option" error was first raised in Moodle 3.11. The commandline option --supportemail was first introduced in Moodle 4.1, which means all versions between 3.9 and 4.1 are affected.

See GitHub Action job result: https://github.com/geoffreyvanwyk/ansible-role-moodle/actions/runs/6323468486/job/17171086454#step:5:277

The latest Moodle version is 4.3. The role should allow for its installation by setting the required PHP version.

If the parent of the deployment destination directory, {{ moodle_deploy_destination | dirname }}, already exists, it should keep its original owner, group and mode to avoid any unforeseen repurcussions.

Rather use access control lists to give the Ansible user write access to it.

This will involve creating a tag for v1.0.0. The GitHub workflow will do the rest.

This is because a random password is assigned to the user which changes every time, because we do not want the password stored in the source code. A solution would be to first check if the user already exists without assigning a password (if possible), then assigning the password if the user did not already exist.