Quote From : Brijesh August 5, 2026, 11:29 am
Moodle requires the core files to be present exactly one directory above the public files so if you upload the public files to /public_html/site2/ it will need the core files in /public_html/ which would be web accessible and insecure.
There is currently no way to notify Moodle that the core file exists in another directory.
If you were able to configure this manually do let us know the steps you followed so we can try to replicate the same.
Hi Brijesh, sorry for the delay on the answer.
I misspelled it, my bad; I wasn't referring to the core files, but to the moodledata dir.
I will try to explain our problem again from a different angle. Take this installation:
- Moodledata files -> /home/user/public_html/moodledata/
- Moodle core files -> /home/user/public_html/site1/
- Moodle public files -> /home/user/public_html/site1/public/
On this server, /home/user/public_html/ is a public directory, and Moodle domain is targeting /home/user/public_html/site1/public/. We can manually install a Moodle like this, because the CMS can't check if /home/user/public_html/ is public or not.
But Softaculous forbids this installation, because it is able to check that /home/user/public_html/ is in fact public.
Could you implement a checkbox to override the Moodle security checks, and let an installation like this one happen? Softaculous forces Moodle to be installed on a fully private enviroment ( except for /site1/public/ ), wich is nice on a vacumm, but in reality this de facto forbids the installation on lots of existing accounts that have a domain pointing to public_html.
The installation on a fully private enviroment, if adviseable, maybe should not be mandatory.]]>