貼文的作者是 Visvanath Ratnaweera

Besonders aktive Moodler的相片 Translators的相片
Du bist in Moodle 5.1 und es gibt ein /var/www/moodle/public/admin/cli/upgrade.php wie oben beschrieben? Dann stimmt was nicht. Das admin/cli/ Verzeichnis befindet sich unter /var/www/moodle/ (ohne public/).
 
Oder mit "läuft das Update durch!" meinst du, als das Plugin weg ist, hat Moodle automatisch die webbasierte (Nutzer "admin" auf Webinterface) Upgrade ausgeloest? 
Particularly helpful Moodlers的相片 Translators的相片
Me thinks that the request to generalize "Mastodon URL" to "Fediverse URL" is altruistic. Fediverse is too diverse to agree on a unified URL. The most general "handle" is IMHO @callname@instance. 'callname' beeing the name shown as the owner, 'instance' is the FQDN of the server, that offers some sort of social network, like Mastodon (micro-blogging), Pixelfeld (photo sharing).

I don't think moodle.org is interested in people's photo collections or video collections (peertube). This field is the successor to the Twitter ID (through the mad X Boooh ID). So micro-blogging, means Mastodon. If we agree on that then "Mastodon URL" is correct.

Now about the second part, "URL": @callname@instance is not a URL, it is the "handle" as Mastodon and possibly other Fediverse services understan. But you can convert it to a URL to display on the browser. That would be https://instance/@callname.

So moodle.org has a choice. Call the field:
a) Mastodon handle. Expect @callname@instance. The clever programmers can convert it to a hyperlink https://instance/@callname
b) Mastodon URL. Expect https://instance/@callname directly,. A filter would convert it to a hyperlink.
Particularly helpful Moodlers的相片 Translators的相片

Hi

These forums are n-to-n, everybody can ask, anybody can answer! In this particular topic somebody else has to answer, server clusters is not my topic. 10 machine web cluster and 4 machine database cluster is a complicated operation. The people who run that kind of infrastructure have separated from this forum. See A new "Large scale Moodle deployment" support group.

The basic principles are always the same, see Performance recommendations. You need to monitor a full matrix of server internals and during load, simulated or real, find out the bottleneck. Make it broader. But there will always be one. The complication is, the scale is non-linear. As things get congested unexpected things start to happen due to the processes blocking the others.

Pl. see Server cluster. Unfortunately, the clustering brings its own overhead which deteriorates the net output. Treating them is much more complicated. We hear of cases clusters delivering less than one beefy server. The obvious candidate is the network, most notoriously the network mounted file system(s). NFS doesn't have a good reputation. The alternatives are not that simple.

Read the many past discussions in this forum on this subject. But at the level you are operating, you need a specialist on the subject. Definitely beyond me.

評比平均分數:Useful (2)
Particularly helpful Moodlers的相片 Translators的相片

12 December 2025

Thoughtfully Shaping Our Digital Future

To the parties forming the government in the Senate and House of Representatives, as well as the outgoing administration,

https://openletter.earth/zorgvuldig-and-zorgzaam-digitaal-f559037e

(found in Mastodon somewhere..)

評比平均分數: -