That’s the main point. I would take one of this two options:
Devise an event nethserver-moodle-update to check and change SQL accordingly to user inputs (enable/disable integration in the WebGUI or following the status of the system when installing), thus satisfying the needs for manageability from the NS WebGUI;
Leave completely the integration of AD/LDAP to the sysadmin.
I do think also the first one is feasible, but I don’t want to leave all the fun to you
Unfortunately I have a queue of stuff to do (for BgLUG, for TDF, for some schools, for this community) that I really don’t know when I’m able to check for it. Do you happen to know someone that sells some ubiquity, an additional pair of hands or additional 24 hours a day?
The Server Manager Users&Groups page sets only a minimal set of attributes. Additional attributes could be managed by other clients, like “phpLDAPadmin”, “AD RSAT tools”, or - why not - moodle itself.
I was talking about Moodle with @robb and others recently so I just installed Moodle 3.4 which needs PHP 7 which I took from nethserver-php-scl by @stephdl :
tried postgres 9.6 from SCL without success, now mariadb with mariadb connector is used
PHP 7.1
custom template /etc/e-smith/templates-custom/etc/opt/remi/php71/php.ini/90moodle for PHP7.1 settings
/etc/my.cnf.d/moodle.cnf for mysql config
This is just for the installation of the new version, for extra settings like AD check the first post of @robb and following…just copy/paste the following to a terminal:
Thanks a lot @mrmarkuz!
I also tried to install Moodle3.4, but did another approach: instead of installing in /var/www/html, I created a vhost and installed in /var/lib/nethserver/vhost/
Pro for this approach is tou can choose php7.x from netgui. I ran into problems that look liked a CSS problem. Con was that even though I changed permissions of the vhost to apache, the configuration script of Moodle during web install part went sour…
If php-scl can be used when installing in /var/www/html by using a custom template (wish I could create them… would love to get some insight info on that) It will be a lot easier to install.
In the previous version of Moodle (3.1, created by @areguera) there is a nice way of creating a custom url. Can this code be re-used for Moodle 3.4?
I noticed that Moodle writes a wwwroot property to its config file. When you connect via http at install it writes http to config and if you connect via https afterwards you have the CSS problem.
Here is the creation of the custom template for PHP7.1. I copied the content from the Moodle homepage.
It’s described here.
I am not a dbadmin and didn’t know that before I read the article but the GRANT command invokes a FLUSH. I know it’s used in plenty of tutorials but it seems to be obsolete.
Please check if the directory /var/www/html/moodle exists.
You simply could run the whole procedure again, existing db is kept.
Well, obviously I am no DBA either… thnx for the pointer…
the moodle dir exists (as I copied the untarred moodle dir to the /var/www/html dir…) and changed permissions…
I will go over the whole procedure again to see what happens…
In /var/log/hhtpd/ssl_access_log I see several attempts to access the moodle directory by me:
213.49.121.74 - - [13/Feb/2018:16:46:27 +0100] “GET /moodle/ HTTP/1.1” 404 205
404 means:
404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
205 means:
205 Reset Content
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
Then we should look into this css problem… I think it is wortth a try to find out because with vhost you can select php7.1 for just that vhost and you don’ t have to force php7.1 globally…
You are right with using a virtual host. I found out that the CSS problem occurs when using https, with http it’s working. I think the problem is (missing) rewriting.