Posts made by Visvanath Ratnaweera

Moodle in English -> Installing and upgrading help -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public. -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public.

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Have realized that "mid November" is not far away! I reset the course and started preparing it. During that time, say one week (till Friday 7 November) the course is open for guests. Have a peek at https://edunet.lk/course/view.php?id=137. Notice that with the Moodle "guest" login, you can't do anything actively. I have a scheme of activity restrictions, so you won't see much of the assignments, let alone participating in them.
Average of ratings: -

Moodle in English -> Installing and upgrading help -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public. -> Hosted Server Moodle Install: Success!

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
> With moodle above public_html, you will still need to create a symbolic link (file) in public_html to point to Moodle 5.1.

Is this the prescribed method or a workaround? From my little understanding of web security, the whole idea of making the "higher" directory inaccessible to the web server is bypassed by this symoblic link!
Average of ratings: Useful (1)

Moodle in English -> Installing and upgrading help -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public. -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public.

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Ken, in https://moodle.org/mod/forum/discuss.php?d=470654#p1889472 there is nothing about a CLI. The only places it remotely resembles a CLI are file and directory (directories are also files, just that they are lists of files) names like /path/to/webroot. Paths are a common concept of all the well-knows OSes today, only that (DOS and) Windows have C:\win32\programs\.. (backword slash) kind of path names whereas Unix, which precedes DOS, used the forward slash right from the beginning. You see the paths even on the Windows GUI. If you navigate the Windows file system in its file explorer (formerly Windows explorer), I think you click or right-click on the path name window to see the full path. Where do you see a CLI?
Average of ratings: -

Moodle in English -> Installing and upgrading help -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public. -> Hostinger Moodle Install Error: Incorrect $CFG->wwwroot in config.php. It should not end in /public.

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators
Yeah, differences in terms an notations are wasting your energy. Here is a feeble try to alleviate that: See Installing Moodle, some terms and their definitions.
Average of ratings: -

Moodle in English -> Installing and upgrading help -> Moodle 5.1 in a hosted server subfolder - Upgrading docs are incorrect. -> Installing Moodle, some terms and their definitions

by Visvanath Ratnaweera -
Picture of Particularly helpful Moodlers Picture of Translators

Hi Rick and the others

Since you all concentrate on careful documentation, see also https://moodle.org/mod/forum/discuss.php?d=470563, I thought some terms and their definitions  would help to avoid the recurring discussions. Here's a try, starting from the least controversial.

  1. Domain: A short form for domain name. For example foo.example.com, bar.example.com and example.com itself are all domains. If one wants to avoid confusions with other uses of the term, one could say FQDN.
  2. Web root, aka : When the URL (see also URL) of a web resource contains only the domain, eg. https://foo.example.com, the web server delivers the default content (index.html, index.php,..) in the web root. This is sometimes called the document root or DocumentRoot, since that is what Apache calls it. Nginx calls it just root.
  3. (Web) Site: This has multiple meanings.
    1. Just the URL of a web site, e.g. https://foo.example.com.
    2. The landing page (homepage) of a web site (what you see when you visit its 'home' URL)
    3. The domain, as in 1). This is typical among the system administrators, since it is unique to each web site his machine serves, he prefers to name thing starting with the domain, e.g. the root of the web site https://foo.example.com will be /some/path/foo.example.com/.

Now, how to overcome this ambiguity? I would say, the system admin can name things the way he wants in his machine, but the documentation needs neutral terms. My suggestions are:

  1. Domain > as above
  2. Web root > as above
  3. Site: Avoid using it in naming directories (in the documentation), use /path/to/webroot instead. Of course you have show examples of /path/to/webroot when you introduce it.

BTW, In Unix and in many other early operating systems, collections of files were called directories. The term folder came from Microsoft in their desktop analogy (borrowed from AT&T). They are experts in using everyday terms as technical jargon and subtly influencing our thinking. The MS Word is the parade example - not to mention the excel sheets and (pointless) PowerPoints. Or nowadays people using 'app' to mean desktop applications, server applications, oil bandages or just anything that applies! Yeah, the first step in liberating ourselves from the BIG TECH should start with out thinking (immediately followed by the terms we use).

Average of ratings: -