@Ken, the NAS is my private device, at home, and got it so I could use it as an out of the box web server. I saw one in operation and was impressed by the fact that not only did it work, it was accessible from work to the owner's home. Thought it would be ideal for what I wanted, and will be when set up properly.
I am now admining a small Moodle, again, and they are currently on a v3.1.x and want to update to a v3.4.x about September/October, so are planning for it now. (These guys are so well organized, a pleasure to work with them.) Currently, they are using on their Linux/Apache/MariaDB/PHP stack PHP v5.6.
While I am admining the Moodle for them, as they really wanted someone outside to let them know if something was not working, They could do it, but their idea is if they have me, or someone like me, I am going to let them know when they are getting it wrong, or they can be alerted to issues before they become major. Works for them, and I am happy they are quite prepared to put up with me. Works all round...
I have access to the Moodle, the code base the Database, the moodledata directory, but that is all. That is not a problem because my Linux knowledge is, politely, limited (although learning lots lately). All this is set to a backdrop of me being a teacher, in a high school, with little time and few resources except for what I can make myself.
While working on my Moodle a v 3.2.4, I looked at what PHP it was using, and found it was using a v5.6. I checked the production site and saw it too was using PHP v5.6. I know I have a v7.0 of PHP and looking at the specs for Moodle v3.4, saw that PHP v7.0 was recommended. I wasn't sure if my production site have PHP v7.0, they haven't yet but that is a planned upgrade too. My NAS Moodle is using PHP v5.6 despite having v7.0 on the system.
Until I put phpMyAdmin on the NAS, I only had PHP v7.0, but phpMyAdmin doesn't use v7.0, only v5.6.
I thought I could change where Moodle gets its PHP config file, within Moodle code, but apparently not. I can access the Apache httpd.config and the php.ini files on the NAS, but not on the production site server. I thought if there was a way to force Moodle to use a particular version of PHP, then I could pass that on to the server manager, solve a potential problem before it becomes a problem. I wouldn't just be relying upon the automaticity of Moodle to sort it for itself, that's all.
But this is now way outside of Moodle's purview I suggest, and should be a dead topic.
Thanks for the suggestions though, really appreciate the time you, Visvanath, Al and Howard have spent on it.
Cheers...