Howard Miller

Ok - so what is your concern, here?

Applications like Zap give you advice that you might want to think about. They are not absolute. Zap doesn't know how Moodle works.

Why do you think this is an issue?

 

Are you using the optional CSP plugin?  Why did you install the CSP blocker?  

 

I'm not sure what problem you're trying to fix...

I would go and take a serious look at Enterprise MySQL (MySQL potentially works fine at scale).

You may also want to consider engaging the services of a Moodle Partner who is experienced in this kind of thing.

NFS is fine for storage but you MUST have proper cache storage (eg. Redis) as caching to shared disk will be very slow.

I'd be very reluctant to simply delete data out of the database. There are all sorts of relationships you may not be aware of.

The best plan is to organise your courses - or bits of courses - on a year by year basis. Then when you no longer need the data from those courses, delete the year.

You can also use the privacy functions to define rules about user data (and completely delete them). But good luck understanding it all

You can't run cron through the web interface by default. It's disabled for security reasons.

The documentation for cron is here - Cron

It all depends on what your server OS is and how you installed Moodle. If you have any questions when you've read the docs, let us know