So anyone has the freedom to choose either docker or native way in order to have a manual web-based moodle installation either way is fine. In the first place is desighned to fit the needs of a specific organization as you can see and I offer some encahncements.
Also if your server has a problem you can move your moodle installation it easily because you are moving a whole system and not just an app into another machine and work just fine.
Also many platforms such as azure offers you docker technology to run an application so you do not bother with server stuff to much I guess you just do whaterver to run in to your pc and then launch. The whole point is that when a new mooble major version comes out the image will be rebuilt. I don't see from a Moodle point of view anyway that there is a difference between security updates and any other sort of updates.
I do not know yet, I have aknoledgement about docker but on moodle itself I have still ways to go. But docker provides volume mechanism to share between docker images and the system itself specific folders. I did that with wordpress using the correct cli tool I guess with moodle the same principle will get applied.
So all I need is to have the correct folder as a volume and run te correct cli tool. The whole one-click install actually is one command run a script that does all the dirty job of setting up moodle updating pluginc etc etc. In the end what I do is a fully cli way to install moodle using scripts to do whatever you type to console manually, that's the only difference.
Dimitrios Desyllas, this is a containerized Moodle built by a Docker veteran, maybe you will like it too. As I said earlier I've read quite a lot about docker lots of hype certainly and just cannot figure out what I would need it for. It's takes 5 mins to install Moodle. Why do I need another layer of complexity? Sorry if I'm missing something. I often am. Maybe for the same reasons that we need package managers, when we actually can compile everything from the source code.
I looked at your scripts and they seem to use Moosh to configure Moodle in a particular way that suits you but won't suit me. I have to install a bunch of other stuff to get to that point. If I want to automate Moodle installation because I have loads of sites to install I can - and have. I have some shell scripts to do it.
It's simple and it works. I've yet to see a package manager style version of Moodle that doesn't cause more problems than it solves. I don't mean to "pour cold water" on your efforts - just my experience. However, I always have to look up Iaas, PaaS and all those other ones because I can't remember what they mean.
I am almost certainly not your target audience. If your installing Moodle 2. Searching the forums on this issue is really confusing. We really ought to have different forums for the versions Last time I saw this message it was because the wrong database type was included in the config. This is why the previous advice of letting Moodle create the config. Letting Moodle create the config.
Manually entering mysql as database type leads to the error above - but my question now is Anyone got additional info on this please? Now I understand that MySQL is indeed supported, but Moodle will only work with a good deal of work involving multiple php. The MySQLi extension is very standard. Where are you getting your PHP from that it does not this library available and enabled by default?
Databases have a "Character set" and a "Collation". You may get the option to set these values when you create the database. If you are not given a choice, the default options are probably good.
An install on an old server may have the wrong settings. Enter the password you previously set - or been given - for the MySQL 'root' user. If this is available you can use it to create a new database.
If you have installed several Moodle installations on the same server, there will be several databases in your MySQL server.
0コメント